Browse Source

clarify CCYY is expected to be four digits, even though XML Schema allows for more.

xep-0352-v0.2
Peter Saint-Andre 4 years ago
parent
commit
1b7a6faf3f
2 changed files with 6 additions and 6 deletions
  1. 4
    4
      xep-0082.xml
  2. 2
    2
      xep.ent

+ 4
- 4
xep-0082.xml View File

@@ -80,7 +80,7 @@
<p>The following acronyms and characters are used herein to represent time-related concepts:</p>
<table caption='Acronyms and Characters'>
<tr><th>Term</th><th>Definition</th></tr>
<tr><td>CCYY</td><td>four-digit year portion of Date</td></tr>
<tr><td>CCYY</td><td>four-digit year portion of Date <note>According to the XML schema datatypes specification &lt;<link url='http://www.w3.org/TR/xmlschema11-2/#dateTime'>http://www.w3.org/TR/xmlschema11-2/#dateTime</link>&gt;, the year portion of a Date can be more than four digits (for years after 9999) and can be preceded by a minus sign (for years before 1 BCE); given that Jabber/XMPP technologies did not exist before 1999, the use of the minus sign is not recommended.</note></td></tr>
<tr><td>MM</td><td>two-digit month portion of Date</td></tr>
<tr><td>DD</td><td>two-digit day portion of Date</td></tr>
<tr><td>-</td><td>ISO 8601 separator among Date portions</td></tr>
@@ -102,7 +102,7 @@
<code>
CCYY-MM-DD
</code>
<p>This profile is equivalent to the 'date' datatype defined in XML Schema <note>The 'date' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema-2/#date'>http://www.w3.org/TR/xmlschema-2/#date</link>&gt;.</note>. When an XML schema is used to define an XMPP protocol extension that uses this profile, the datatype MUST be an XML Schema 'date'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<p>This profile is equivalent to the 'date' datatype defined in XML Schema <note>The 'date' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema11-2/#date'>http://www.w3.org/TR/xmlschema11-2/#date</link>&gt;.</note>. When an XML schema is used to define an XMPP protocol extension that uses this profile, the datatype MUST be an XML Schema 'date'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<example caption='The date of American independence'>
1776-07-04
</example>
@@ -113,7 +113,7 @@
CCYY-MM-DDThh:mm:ss[.sss]TZD
</code>
<p>The Time Zone Definition is mandatory and MUST be either UTC (denoted by addition of the character 'Z' to the end of the string) or some offset from UTC (denoted by addition of '[+|-]' and 'hh:mm' to the end of the string). The fractions of a second are optional and MAY be ignored if included (although an XMPP protocol extension using the DateTime profile MAY require the fractions of a second).</p>
<p>This profile is equivalent to the 'dateTime' datatype defined in XML Schema <note>The 'dateTime' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema-2/#dateTime'>http://www.w3.org/TR/xmlschema-2/#dateTime</link>&gt;.</note>. When an XML schema is used to define a Jabber protocol that uses this profile, the datatype MUST be an XML Schema 'dateTime'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<p>This profile is equivalent to the 'dateTime' datatype defined in XML Schema <note>The 'dateTime' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema11-2/#dateTime'>http://www.w3.org/TR/xmlschema11-2/#dateTime</link>&gt;.</note>. When an XML schema is used to define a Jabber protocol that uses this profile, the datatype MUST be an XML Schema 'dateTime'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<example caption='Datetime of the first human steps on the Moon (UTC)'>
1969-07-21T02:56:15Z
</example>
@@ -127,7 +127,7 @@
hh:mm:ss[.sss][TZD]
</code>
<p>The Time Zone Definition is optional; if included, it MUST be either UTC (denoted by addition of the character 'Z' to the end of the string) or some offset from UTC (denoted by addition of '[+|-]' <note>Inclusion of the '+' character means that the time in that zone is ahead of UTC; e.g., a Time Zone Definition of "+07:00" means that if the UTC time is 12:00 then the local time is 19:00 (typically this is true of an area that is east of 0&#176; degrees latitude and west of 180&#176; latitude, such as Bangkok, Thailand). Inclusion of the '-' character means that the time in that zone is behind UTC; e.g., a Time Zone Definition of "-07:00" means that if the UTC time is 12:00 then the local time is 05:00 (typically this is true of an area that is west of 0&#176; degrees latitude and east of 180&#176; latitude, such as Denver, Colorado, USA).</note> and 'hh:mm' to the end of the string). The fractions of a second are optional and MAY be ignored if included (although a Jabber protocol using the DateTime profile MAY require the fractions of a second).</p>
<p>This profile is equivalent to the 'time' datatype defined in XML Schema <note>The 'time' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema-2/#time'>http://www.w3.org/TR/xmlschema-2/#time</link>&gt;.</note>. When an XML schema is used to define a Jabber protocol that uses this profile, the datatype MUST be an XML Schema 'time'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<p>This profile is equivalent to the 'time' datatype defined in XML Schema <note>The 'time' datatype is defined at &lt;<link url='http://www.w3.org/TR/xmlschema11-2/#time'>http://www.w3.org/TR/xmlschema11-2/#time</link>&gt;.</note>. When an XML schema is used to define a Jabber protocol that uses this profile, the datatype MUST be an XML Schema 'time'. If there are differences between the description in this document and those in XML Schema, the latter overrule.</p>
<example caption='Time for tea'>
16:00:00
</example>

+ 2
- 2
xep.ent View File

@@ -308,8 +308,8 @@ THE SOFTWARE.
<!ENTITY w3xml "<span class='ref'><link url='http://www.w3.org/TR/REC-xml/'>XML 1.0</link></span> <note>Extensible Markup Language (XML) 1.0 (Fourth Edition) &lt;<link url='http://www.w3.org/TR/REC-xml/'>http://www.w3.org/TR/REC-xml/</link>&gt;.</note>" >
<!ENTITY w3xmlenc "<span class='ref'><link url='http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/'>XML Encryption</link></span> <note>XML Encryption Syntax and Processing &lt;<link url='http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/'>http://www.w3.org/TR/2002/REC-xmlenc-core-20021210/</link>&gt;.</note>" >
<!ENTITY w3xmlnamespaces "<span class='ref'><link url='http://www.w3.org/TR/REC-xml-names/'>Namespaces in XML</link></span> <note>Namespaces in XML &lt;<link url='http://www.w3.org/TR/REC-xml-names/'>http://www.w3.org/TR/REC-xml-names/</link>&gt;.</note>" >
<!ENTITY w3xmlschema1 "<span class='ref'><link url='http://www.w3.org/TR/xmlschema-1/'>XML Schema Part 1</link></span> <note>XML Schema Part 1: Structures &lt;<link url='http://www.w3.org/TR/xmlschema-1/'>http://www.w3.org/TR/xmlschema-1/</link>&gt;.</note>" >
<!ENTITY w3xmlschema2 "<span class='ref'><link url='http://www.w3.org/TR/xmlschema-2/'>XML Schema Part 2</link></span> <note>XML Schema Part 2: Datatypes &lt;<link url='http://www.w3.org/TR/xmlschema-2/'>http://www.w3.org/TR/xmlschema-2/</link>&gt;.</note>" >
<!ENTITY w3xmlschema1 "<span class='ref'><link url='http://www.w3.org/TR/xmlschema11-1/'>XML Schema Part 1</link></span> <note>XML Schema Part 1: Structures &lt;<link url='http://www.w3.org/TR/xmlschema11-1/'>http://www.w3.org/TR/xmlschema11-1/</link>&gt;.</note>" >
<!ENTITY w3xmlschema2 "<span class='ref'><link url='http://www.w3.org/TR/xmlschema11-2/'>XML Schema Part 2</link></span> <note>XML Schema Part 2: Datatypes &lt;<link url='http://www.w3.org/TR/xmlschema11-2/'>http://www.w3.org/TR/xmlschema11-2/</link>&gt;.</note>" >
<!ENTITY w3xmlsig "<span class='ref'><link url='http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/'>XML Signature</link></span> <note>XML Signature Syntax and Processing &lt;<link url='http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/'>http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/</link>&gt;.</note>" >
<!ENTITY w3xop "<span class='ref'><link url='http://www.w3.org/TR/xop10/'>XML-binary Optimized Packaging</link></span> <note>XML-binary Optimized Packaging &lt;<link url='http://www.w3.org/TR/xop10/'>http://www.w3.org/TR/xop10/</link>&gt;.</note>" >
<!ENTITY w3xpath "<span class='ref'><link url='http://www.w3.org/TR/xpath'>XPath</link></span> <note>XML Path Language &lt;<link url='http://www.w3.org/TR/xpath'>http://www.w3.org/TR/xpath</link>&gt;.</note>" >

Loading…
Cancel
Save