XsdDateTime#
Fully qualified primitivetype name of the UML model DDI-CDI 1.1beta: DDICDIModels::DDICDILibrary::DataTypes::XMLSchemaDataTypes::XsdDateTime
Definition#
Primitive data type “dateTime” of the XML Schema data types.
Definition from XML Schema Part 2: Datatypes Second Edition: ‘dateTime values may be viewed as objects with integer-valued year, month, day, hour and minute properties, a decimal-valued second property, and a boolean timezoned property. Each such object also has one decimal-valued method or computed property, timeOnTimeline, whose value is always a decimal number; the values are dimensioned in seconds, the integer 0 is 0001-01-01T00:00:00 and the value of timeOnTimeline for other dateTime values is computed using the Gregorian algorithm as modified for leap-seconds. The timeOnTimeline values form two related “timelines”, one for timezoned values and one for non-timezoned values. Each timeline is a copy of the ·value space· of decimal, with integers given units of seconds.
The ·value space· of dateTime is closely related to the dates and times described in ISO 8601. For clarity, the text above specifies a particular origin point for the timeline. It should be noted, however, that schema processors need not expose the timeOnTimeline value to schema users, and there is no requirement that a timeline-based implementation use the particular origin described here in its internal representation. Other interpretations of the ·value space· which lead to the same results (i.e., are isomorphic) are of course acceptable.
All timezoned times are Coordinated Universal Time (UTC, sometimes called “Greenwich Mean Time”). Other timezones indicated in lexical representations are converted to UTC during conversion of literals to values. “Local” or untimezoned times are presumed to be the time in the timezone of some unspecified locality as prescribed by the appropriate legal authority; currently there are no legally prescribed timezones which are durations whose magnitude is greater than 14 hours. The value of each numeric-valued property (other than timeOnTimeline) is limited to the maximum value within the interval determined by the next-higher property. For example, the day value can never be 32, and cannot even be 29 for month 02 and year 2002 (February 2002).’ For details see https://www.w3.org/TR/xmlschema-2/#dateTime.
Diagram#
Diagram
Usage#
Encodings#
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 XsdDateTime (entire model as XMI)
1<packagedElement xmlns:StandardProfile="http://www.omg.org/spec/UML/20131001/StandardProfile"
2 xmlns:uml="http://www.omg.org/spec/UML/20131001"
3 xmlns:xmi="http://www.omg.org/spec/XMI/20131001"
4 xmi:id="DDICDIModels-DDICDILibrary-DataTypes-XMLSchemaDataTypes-XsdDateTime"
5 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#XsdDateTime"
6 xmi:type="uml:PrimitiveType">
7 <ownedComment xmi:id="DDICDIModels-DDICDILibrary-DataTypes-XMLSchemaDataTypes-XsdDateTime-ownedComment"
8 xmi:uuid="http://ddialliance.org/Specification/DDI-CDI/1.0/XMI/#XsdDateTime-ownedComment"
9 xmi:type="uml:Comment">
10 <annotatedElement xmi:idref="DDICDIModels-DDICDILibrary-DataTypes-XMLSchemaDataTypes-XsdDateTime"/>
11 <body>Definition
12============
13Primitive data type "dateTime" of the XML Schema data types.
14
15Definition from XML Schema Part 2: Datatypes Second Edition:
16'dateTime values may be viewed as objects with integer-valued year, month, day, hour and minute properties, a decimal-valued second property, and a boolean timezoned property. Each such object also has one decimal-valued method or computed property, timeOnTimeline, whose value is always a decimal number; the values are dimensioned in seconds, the integer 0 is 0001-01-01T00:00:00 and the value of timeOnTimeline for other dateTime values is computed using the Gregorian algorithm as modified for leap-seconds. The timeOnTimeline values form two related "timelines", one for timezoned values and one for non-timezoned values. Each timeline is a copy of the &#183;value space&#183; of decimal, with integers given units of seconds.
17
18The &#183;value space&#183; of dateTime is closely related to the dates and times described in ISO 8601. For clarity, the text above specifies a particular origin point for the timeline. It should be noted, however, that schema processors need not expose the timeOnTimeline value to schema users, and there is no requirement that a timeline-based implementation use the particular origin described here in its internal representation. Other interpretations of the &#183;value space&#183; which lead to the same results (i.e., are isomorphic) are of course acceptable.
19
20All timezoned times are Coordinated Universal Time (UTC, sometimes called "Greenwich Mean Time"). Other timezones indicated in lexical representations are converted to UTC during conversion of literals to values. "Local" or untimezoned times are presumed to be the time in the timezone of some unspecified locality as prescribed by the appropriate legal authority; currently there are no legally prescribed timezones which are durations whose magnitude is greater than 14 hours. The value of each numeric-valued property (other than timeOnTimeline) is limited to the maximum value within the interval determined by the next-higher property. For example, the day value can never be 32, and cannot even be 29 for month 02 and year 2002 (February 2002).'
21For details see https://www.w3.org/TR/xmlschema-2/#dateTime.
22
23
24</body>
25 </ownedComment>
26 <name>XsdDateTime</name>
27</packagedElement>
Fragment for the data type XsdDateTime (entire XML Schema)
1<!-- XML Schema primitive: -->
Fragment for the data type XsdDateTime (entire JSON Schema)
1"dt-XsdDateTime": {
2 "description": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/XsdDateTime",
3 "type": ["object"],
4 "properties": {
5
6 "@type": {
7 "const": "XsdDateTime"
8 }
9 },
10 "required": ["@type"],
11 "additionalProperties": false
12},
Fragment for the data type XsdDateTime (main ontology)
1# datatype XsdDateTime
2# based on the UML data type DDICDIModels::DDICDILibrary::DataTypes::XMLSchemaDataTypes::XsdDateTime
3cdi:XsdDateTime
4 a rdfs:Class, owl:Class, ucmis:StructuredDataType;
5 rdfs:label "XsdDateTime";
6 rdfs:comment "Definition\n============\nPrimitive data type \"dateTime\" of the XML Schema data types.\n\nDefinition from XML Schema Part 2: Datatypes Second Edition:\n'dateTime values may be viewed as objects with integer-valued year, month, day, hour and minute properties, a decimal-valued second property, and a boolean timezoned property. Each such object also has one decimal-valued method or computed property, timeOnTimeline, whose value is always a decimal number; the values are dimensioned in seconds, the integer 0 is 0001-01-01T00:00:00 and the value of timeOnTimeline for other dateTime values is computed using the Gregorian algorithm as modified for leap-seconds. The timeOnTimeline values form two related \"timelines\", one for timezoned values and one for non-timezoned values. Each timeline is a copy of the ·value space· of decimal, with integers given units of seconds.\n\nThe ·value space· of dateTime is closely related to the dates and times described in ISO 8601. For clarity, the text above specifies a particular origin point for the timeline. It should be noted, however, that schema processors need not expose the timeOnTimeline value to schema users, and there is no requirement that a timeline-based implementation use the particular origin described here in its internal representation. Other interpretations of the ·value space· which lead to the same results (i.e., are isomorphic) are of course acceptable.\n\nAll timezoned times are Coordinated Universal Time (UTC, sometimes called \"Greenwich Mean Time\"). Other timezones indicated in lexical representations are converted to UTC during conversion of literals to values. \"Local\" or untimezoned times are presumed to be the time in the timezone of some unspecified locality as prescribed by the appropriate legal authority; currently there are no legally prescribed timezones which are durations whose magnitude is greater than 14 hours. The value of each numeric-valued property (other than timeOnTimeline) is limited to the maximum value within the interval determined by the next-higher property. For example, the day value can never be 32, and cannot even be 29 for month 02 and year 2002 (February 2002).'\nFor details see https://www.w3.org/TR/xmlschema-2/#dateTime."@en;
7
8 owl:hasKey ();
9.
Fragment for the data type XsdDateTime (entire JSON-LD)
1{
2 "@context": [
3 {
4 "cdi": "http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/",
5 "xsd": "http://www.w3.org/2001/XMLSchema#",
6
7
8 " comment ": "tag:json-should-support-trailing-commas"
9 }
10 ],
11 "generatedBy": "This code was generated by the Eclipse Acceleo project UCMIS M2T on 2026-04-15 14:38:44.",
12 "basedOn": "based on the UML data type DDICDIModels::DDICDILibrary::DataTypes::XMLSchemaDataTypes::XsdDateTime"
13}
Fragment for the data type XsdDateTime (entire SHACL - Shapes Constraint Language)
1# datatype XsdDateTime
2# based on the UML data type DDICDIModels::DDICDILibrary::DataTypes::XMLSchemaDataTypes::XsdDateTime
3<#XsdDateTime> a sh:NodeShape;
4 sh:targetClass cdi:XsdDateTime;
5 sh:message "See http://ddialliance.org/Specification/DDI-CDI/1.0/RDF/XsdDateTime";
6 sh:closed true;
7 sh:ignoredProperties ( owl:sameAs );
8 sh:property [
9 sh:path rdf:type;
10 sh:in ( cdi:XsdDateTime
11 ) ;
12 ];
13 # attributes
14
15
16
17.
Fragment for the data type XsdDateTime (entire ShEx - Shape Expressions)
1# datatype XsdDateTime
2# based on the UML data type DDICDIModels::DDICDILibrary::DataTypes::XMLSchemaDataTypes::XsdDateTime
3cdi:XsdDateTimeShape CLOSED {
4 a [cdi:XsdDateTime];
5 }