CombinedDate¶
Fully qualified datatype name: DDICDIModels::DDICDILibrary::DataTypes::StructuredDataTypes::CombinedDate
Definition¶
Provides the structure of a single Date expressed in an ISO date structure along with equivalent expression in any number of non-ISO formats. While it supports the use of the ISO time interval structure this should only be used when the exact date is unclear (i.e. occurring at some point in time between the two specified dates) or in specified applications. Ranges with specified start and end dates should use the DateRange as a datatype. Commonly uses property names include: eventDate, issueDate, and releaseDate.
Explanatory notes¶
Date allows one of a set of date-time (YYYY-MM-DDThh:mm:ss), date (YYYY-MM-DD), year-month (YYYY-MM), year (YYYY), time (hh:mm:ss) and duration (PnYnMnDnHnMnS), or time interval (YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss, YYYY-MM-DDThh:mm:ss/PnYnMnDnHnMnS, PnYnMnDnHnMnS/ YYYY-MM-DDThh:mm:ss) which is formatted according to ISO 8601 and backed supported by regular expressions in the BaseDateType. Time Zone designation and negative/positive prefixes are allowed as are dates before and after 0000 through 9999.
Diagram
Attributes
Name |
Inherited from |
Description |
Data Type |
Multiplicity |
Default value |
|---|---|---|---|---|---|
isoDate |
- own datatype - |
Strongly recommend that ALL dates be expressed in an ISO format at a minimum. A single point in time expressed in an ISO standard structure. Note that while it supports an ISO date range structure this should be used in Date only when the single date is unclear i.e. occurring at some time between two dates. |
0..1 |
||
nonIsoDate |
- own datatype - |
A simple date expressed in a non-ISO date format, including a specification of the date format and calendar used. |
0..* |
||
semantics |
- own datatype - |
Use to specify the type of date. This may reflect the refinements of dc:date such as dateAccepted, dateCopyrighted, dateSubmitted, etc. |
0..1 |
Usage
Type |
Package |
Classifier |
Attribute |
|---|---|---|---|
Class |
Representations |
authorizationDate |
|
Class |
Representations |
releaseDate |
|
Class |
Representations |
releaseDate |
|
DataType |
StructuredDataTypes |
date |
|
DataType |
StructuredDataTypes |
endDate |
|
DataType |
StructuredDataTypes |
startDate |
Syntax representations / encodings
All syntax representations except the Canonical XMI are provided as reference points for specific implementations, or for use as defaults if sufficient in the form presented.
Fragment for the data type CombinedDate (entire XMI model)
1<packagedElement xmlns:StandardProfile="http://www.eclipse.org/uml2/5.0.0/UML/Profile/Standard"
2 xmlns:uml="http://www.eclipse.org/uml2/5.0.0/UML"
3 xmlns:xmi="http://www.omg.org/spec/XMI/20131001"
4 xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate"
6 xmi:type="uml:DataType">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate"/>
11 <body>Definition
12============
13Provides the structure of a single Date expressed in an ISO date structure along with equivalent expression in any number of non-ISO formats. While it supports the use of the ISO time interval structure this should only be used when the exact date is unclear (i.e. occurring at some point in time between the two specified dates) or in specified applications. Ranges with specified start and end dates should use the DateRange as a datatype. Commonly uses property names include: eventDate, issueDate, and releaseDate.
14
15Explanatory notes
16===================
17Date allows one of a set of date-time (YYYY-MM-DDThh:mm:ss), date (YYYY-MM-DD), year-month (YYYY-MM), year (YYYY), time (hh:mm:ss) and duration (PnYnMnDnHnMnS), or time interval (YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss, YYYY-MM-DDThh:mm:ss/PnYnMnDnHnMnS, PnYnMnDnHnMnS/ YYYY-MM-DDThh:mm:ss) which is formatted according to ISO 8601 and backed supported by regular expressions in the BaseDateType. Time Zone designation and negative/positive prefixes are allowed as are dates before and after 0000 through 9999.</body>
18 </ownedComment>
19 <name>CombinedDate</name>
20 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-isoDate"
21 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-isoDate"
22 xmi:type="uml:Property">
23 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-isoDate-ownedComment"
24 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-isoDate-ownedComment"
25 xmi:type="uml:Comment">
26 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-isoDate"/>
27 <body>Strongly recommend that ALL dates be expressed in an ISO format at a minimum. A single point in time expressed in an ISO standard structure. Note that while it supports an ISO date range structure this should be used in Date only when the single date is unclear i.e. occurring at some time between two dates.</body>
28 </ownedComment>
29 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-isoDate-lowerValue"
30 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-isoDate-lowerValue"
31 xmi:type="uml:LiteralInteger"/>
32 <upperValue xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-isoDate-upperValue"
33 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-isoDate-upperValue"
34 xmi:type="uml:LiteralUnlimitedNatural">
35 <value>1</value>
36 </upperValue>
37 <name>isoDate</name>
38 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-XMLSchemaDataTypes-XsdDate"/>
39 </ownedAttribute>
40 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-nonIsoDate"
41 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-nonIsoDate"
42 xmi:type="uml:Property">
43 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-nonIsoDate-ownedComment"
44 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-nonIsoDate-ownedComment"
45 xmi:type="uml:Comment">
46 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-nonIsoDate"/>
47 <body>A simple date expressed in a non-ISO date format, including a specification of the date format and calendar used.</body>
48 </ownedComment>
49 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-nonIsoDate-lowerValue"
50 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-nonIsoDate-lowerValue"
51 xmi:type="uml:LiteralInteger"/>
52 <upperValue xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-nonIsoDate-upperValue"
53 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-nonIsoDate-upperValue"
54 xmi:type="uml:LiteralUnlimitedNatural">
55 <value>*</value>
56 </upperValue>
57 <name>nonIsoDate</name>
58 <isOrdered>true</isOrdered>
59 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-NonIsoDate"/>
60 </ownedAttribute>
61 <ownedAttribute xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-semantics"
62 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-semantics"
63 xmi:type="uml:Property">
64 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-semantics-ownedComment"
65 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-semantics-ownedComment"
66 xmi:type="uml:Comment">
67 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-semantics"/>
68 <body>Use to specify the type of date. This may reflect the refinements of dc:date such as dateAccepted, dateCopyrighted, dateSubmitted, etc.</body>
69 </ownedComment>
70 <lowerValue xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-semantics-lowerValue"
71 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-semantics-lowerValue"
72 xmi:type="uml:LiteralInteger"/>
73 <upperValue xmi:id="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-CombinedDate-semantics-upperValue"
74 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#CombinedDate-semantics-upperValue"
75 xmi:type="uml:LiteralUnlimitedNatural">
76 <value>1</value>
77 </upperValue>
78 <name>semantics</name>
79 <type xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-StructuredDataTypes-ControlledVocabularyEntry"/>
80 </ownedAttribute>
81</packagedElement>
Fragment for the data type CombinedDate (entire XML Schema)
1<xs:element name="CombinedDate"
2 type="CombinedDateXsdType"
3 xml:id="CombinedDate">
4 <!-- based on the UML data type DDICDIModels::DDICDILibrary::DataTypes::StructuredDataTypes::CombinedDate -->
5 <xs:annotation>
6 <xs:documentation>Definition
7 ============
8 Provides the structure of a single Date expressed in an ISO date structure along with equivalent expression in any number of non-ISO formats. While it supports the use of the ISO time interval structure this should only be used when the exact date is unclear (i.e. occurring at some point in time between the two specified dates) or in specified applications. Ranges with specified start and end dates should use the DateRange as a datatype. Commonly uses property names include: eventDate, issueDate, and releaseDate.
9
10 Explanatory notes
11 ===================
12 Date allows one of a set of date-time (YYYY-MM-DDThh:mm:ss), date (YYYY-MM-DD), year-month (YYYY-MM), year (YYYY), time (hh:mm:ss) and duration (PnYnMnDnHnMnS), or time interval (YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss, YYYY-MM-DDThh:mm:ss/PnYnMnDnHnMnS, PnYnMnDnHnMnS/ YYYY-MM-DDThh:mm:ss) which is formatted according to ISO 8601 and backed supported by regular expressions in the BaseDateType. Time Zone designation and negative/positive prefixes are allowed as are dates before and after 0000 through 9999.</xs:documentation>
13 </xs:annotation>
14</xs:element>
15<xs:complexType name="CombinedDateXsdType"
16 xml:id="CombinedDateXsdType">
17 <xs:annotation>
18 <xs:documentation>Definition
19 ============
20 Provides the structure of a single Date expressed in an ISO date structure along with equivalent expression in any number of non-ISO formats. While it supports the use of the ISO time interval structure this should only be used when the exact date is unclear (i.e. occurring at some point in time between the two specified dates) or in specified applications. Ranges with specified start and end dates should use the DateRange as a datatype. Commonly uses property names include: eventDate, issueDate, and releaseDate.
21
22 Explanatory notes
23 ===================
24 Date allows one of a set of date-time (YYYY-MM-DDThh:mm:ss), date (YYYY-MM-DD), year-month (YYYY-MM), year (YYYY), time (hh:mm:ss) and duration (PnYnMnDnHnMnS), or time interval (YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss, YYYY-MM-DDThh:mm:ss/PnYnMnDnHnMnS, PnYnMnDnHnMnS/ YYYY-MM-DDThh:mm:ss) which is formatted according to ISO 8601 and backed supported by regular expressions in the BaseDateType. Time Zone designation and negative/positive prefixes are allowed as are dates before and after 0000 through 9999.</xs:documentation>
25 </xs:annotation>
26 <xs:sequence>
27 <xs:element name="isoDate"
28 type="xs:date"
29 minOccurs="0"
30 maxOccurs="1"
31 xml:id="CombinedDate-isoDate">
32 <xs:annotation>
33 <xs:documentation>Strongly recommend that ALL dates be expressed in an ISO format at a minimum. A single point in time expressed in an ISO standard structure. Note that while it supports an ISO date range structure this should be used in Date only when the single date is unclear i.e. occurring at some time between two dates.</xs:documentation>
34 </xs:annotation>
35 </xs:element>
36 <xs:element name="nonIsoDate"
37 type="NonIsoDateXsdType"
38 minOccurs="0"
39 maxOccurs="unbounded"
40 xml:id="CombinedDate-nonIsoDate">
41 <xs:annotation>
42 <xs:documentation>A simple date expressed in a non-ISO date format, including a specification of the date format and calendar used.</xs:documentation>
43 </xs:annotation>
44 </xs:element>
45 <xs:element name="semantics"
46 type="ControlledVocabularyEntryXsdType"
47 minOccurs="0"
48 maxOccurs="1"
49 xml:id="CombinedDate-semantics">
50 <xs:annotation>
51 <xs:documentation>Use to specify the type of date. This may reflect the refinements of dc:date such as dateAccepted, dateCopyrighted, dateSubmitted, etc.</xs:documentation>
52 </xs:annotation>
53 </xs:element>
54 </xs:sequence>
55</xs:complexType>
Fragment for the data type CombinedDate (main ontology, entire ontology as zip)
1# datatype CombinedDate
2# based on the UML data type DDICDIModels::DDICDILibrary::DataTypes::StructuredDataTypes::CombinedDate
3cdi:CombinedDate
4 a rdfs:Class, owl:Class, ucmis:StructuredDataType;
5 rdfs:label "CombinedDate";
6 rdfs:comment "Definition\n============\nProvides the structure of a single Date expressed in an ISO date structure along with equivalent expression in any number of non-ISO formats. While it supports the use of the ISO time interval structure this should only be used when the exact date is unclear (i.e. occurring at some point in time between the two specified dates) or in specified applications. Ranges with specified start and end dates should use the DateRange as a datatype. Commonly uses property names include: eventDate, issueDate, and releaseDate.\n\nExplanatory notes\n===================\nDate allows one of a set of date-time (YYYY-MM-DDThh:mm:ss), date (YYYY-MM-DD), year-month (YYYY-MM), year (YYYY), time (hh:mm:ss) and duration (PnYnMnDnHnMnS), or time interval (YYYY-MM-DDThh:mm:ss/YYYY-MM-DDThh:mm:ss, YYYY-MM-DDThh:mm:ss/PnYnMnDnHnMnS, PnYnMnDnHnMnS/ YYYY-MM-DDThh:mm:ss) which is formatted according to ISO 8601 and backed supported by regular expressions in the BaseDateType. Time Zone designation and negative/positive prefixes are allowed as are dates before and after 0000 through 9999."@en;
7
8 owl:hasKey (cdi:CombinedDate-isoDate cdi:CombinedDate-nonIsoDate cdi:CombinedDate-semantics);
9.
10
11cdi:CombinedDate-isoDate
12 a rdf:Property, owl:DatatypeProperty, ucmis:Attribute;
13 rdfs:label "isoDate";
14 rdfs:comment "Strongly recommend that ALL dates be expressed in an ISO format at a minimum. A single point in time expressed in an ISO standard structure. Note that while it supports an ISO date range structure this should be used in Date only when the single date is unclear i.e. occurring at some time between two dates."@en;
15 rdfs:domain cdi:CombinedDate;
16 rdfs:range xsd:date;
17.
18
19cdi:CombinedDate-nonIsoDate
20 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
21 rdfs:label "nonIsoDate";
22 rdfs:comment "A simple date expressed in a non-ISO date format, including a specification of the date format and calendar used."@en;
23 rdfs:domain cdi:CombinedDate;
24 rdfs:range cdi:NonIsoDate;
25.
26
27cdi:CombinedDate-semantics
28 a rdf:Property, owl:ObjectProperty, ucmis:Attribute;
29 rdfs:label "semantics";
30 rdfs:comment "Use to specify the type of date. This may reflect the refinements of dc:date such as dateAccepted, dateCopyrighted, dateSubmitted, etc."@en;
31 rdfs:domain cdi:CombinedDate;
32 rdfs:range cdi:ControlledVocabularyEntry;
33.
Fragment for the data type CombinedDate (main JSON-LD entire JSON-LD as zip)
1{
2 "@context": [
3 {
4 "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
5 "xsd": "http://www.w3.org/2001/XMLSchema#",
6 "CombinedDate": "cdi:CombinedDate",
7 "isoDate": {
8 "@id": "cdi:CombinedDate-isoDate",
9 "@type": "xsd:date"
10 },
11 "nonIsoDate": {
12 "@id": "cdi:CombinedDate-nonIsoDate",
13 "@type": "@id",
14 "@context": "NonIsoDate.jsonld"
15 },
16 "semantics": {
17 "@id": "cdi:CombinedDate-semantics",
18 "@type": "@id",
19 "@context": "ControlledVocabularyEntry.jsonld"
20 },
21
22 " comment ": "tag:json-should-support-trailing-commas"
23 }
24 ],
25 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2024-03-16 23:40:13.",
26 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::DataTypes::StructuredDataTypes::CombinedDate"
27}
