Schema_Feb18
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Possible Schema
2
Top-level2nd-level3rd-levelRequiredDescriptionAeon Support ?
3
typesYesPartial. Supports multiple “entity types”, but only one “event type”. Workaround is to allow all facets for all “event types”…
4
idYesJSON-LD style url, or a unique string value (e.g. UUID). May not always be appropriate to have external URL references in certain contexts, so suggest maintaining freedom here for other unique identifier formats.Yes
5
nameYesName of the type. Will be used in display.Yes
6
timeDataYestrue/false. If true, this type has start/end time fields associated with it. Yes-ish.
7
relativeTimeNo. Should only exist if TimeData is true.true/false. Defaults to false. If true, this type has relative time fields rather than absolute fields.Partial. We support relative dates, but cannot support a mix (e.g. some event types being relative, some being absolute).
8
relativeUnitsNo.What units are relative times stored in? e.g. ms, seconds, minutes, hours, etc. or arbitrary ordinal numberNo
9
groupKeyNoIf yes, this type is suitable to use to group together other types.Partial. This is a potential hack to help Aeon separate events and entities so it knows how to treat the different data types.
10
facetsNo.Additional data to be associated with the type. If not provided, assume there is no additional data beyond the defaults (id, label, etc).Partial. Cannot specify additional metadata fields (beyond notes) for entities.
11
idYesJSON-LD style url or a unique string value (e.g. UUID). May not always be appropriate to have external URL references.Yes
12
nameYesJSON label used as object property name? Or should that be ID too? Depends if these are likely to be renamed in future?Yes
13
typeYesThe type of data recorded in this facet. Possible values:
boolean
number
text
spatial information (location... or trajectory? region boundary?)
reference (e.g. to another data object in the timeline)
Partial. No intrinsic support for location, but values can be treated as regular string or could be turned into its own “entity”.
14
referenceTypeYes, if type = reference.The type ID for the associated type. This may be the same as id, but is not guaranteed to be so. Required to support an event having multiple different references back to an object type (e.g. “Person” could be “Developer” or “Tester”Yes
15
multipleNoCan an object have multiple values for this facet? Default: No.Partial. Supports multiple values for relationships to entities only (“reference” in this schema). Does not support multiple values for other properties.
16
allowedNoOptional. If specified, provides an array of allowed values (no others will be accepted). Used to designate a facet as a dropdown list instead of a text field, for instance. If not specified, all values of that type are legal.Partial. Only supports list of options for text properties.
17
18
data
19
idYesYes
20
typeYesThe id of one of the types defined above.Yes-ish.
21
label
* localize
NoThe main display label for this data. This would be the equivalent of an event title, or a person’s name.Yes.
22
absoluteStartYes, if timeData is true and relativeTime is false for this type. Otherwise, should not exist.ISO8601 date representation. For uncertain dates, this should represent the best guess “default” value to use for display purposes in applications that cannot represent uncertainty.Yes-ish. Does not support complete ISO8601 standard yet (BCE dates), but easy fix.
23
absoluteEndNo. Should not exist unless timeData is true and relativeTime is false.ISO8601 date representation. If omitted, event has zero duration. For uncertain dates, this should represent the best guess “default” value to use for display purposes in applications that cannot represent uncertainty.Yes-ish. Does not support complete ISO8601 standard yet (BCE dates), but easy fix.
24
ongoingNo.true/false. Should not be set if an end date is specified?No.
25
uncertainStartNo. Should not exist unless timeData is true and relativeTime is false.EDTF value representing the uncertain date value.No.
26
uncertainEndNo. Should not exist unless timeData is true and relativeTime is false.EDTF value representing the uncertain date value.No.
27
confidence measure??No.Omit this. THey can create a facet.No.
28
relativeStartYes, for “relativeTime” types only.numeric value - milliseconds from arbitrary zero.Yes.
29
relativeEndNo. Only allowed for SupportsRelative types.numeric value - milliseconds from arbitrary zero. If omitted, event has zero duration.Yes.
30
[…]NoAdditional facets, as defined for the typeSee “types” above
31
- facet[type=location]NoLocation representation TBD.
Possibly allow for either a text name (“London”), or {latitude: xx, longitude: yy} object value.
See “types” above
32
- facet[multiple=true]NoFor facets with multiple=true, data is recorded as an array of data. For consistency, array notation required even if only a single value exists at this time.
For example:
facet1: [10] ,
facet2: [“Fred”,”James”,”Bob”]
See “types” above
33
creation_dateNo.ISO8601. The date the file was created.
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
Main menu