rest/datatypes - Revision history

Tantek: en-US

2007-08-31T22:50:33Z

← Older revision		Revision as of 22:50, 31 August 2007
Line 87:		Line 87:
	###SQL's "decimal", perhaps?		###SQL's "decimal", perhaps?
	## If not, how should conforming implementations react to longer integers than they can handle?		## If not, how should conforming implementations react to longer integers than they can handle?
	##*I think integer is fine - we don't have an explict constraint here. Do you want to define +Inf -Inf and NaN ~~behaviour~~? Certainly when building testcases and examples include these.		##*I think integer is fine - we don't have an explict constraint here. Do you want to define +Inf -Inf and NaN behavior? Certainly when building testcases and examples include these.

	# Is it worth deviating from the standard to allow "dateTime" as an alias? (the one case where XML Schema is actually simpler)		# Is it worth deviating from the standard to allow "dateTime" as an alias? (the one case where XML Schema is actually simpler)

DrErnie: /* References */

2006-04-28T16:10:20Z

References

← Older revision		Revision as of 16:10, 28 April 2006
Line 161:		Line 161:
	* Original [http://homepage.mac.com/drernie/plist.html plist] datatype mapping proposal		* Original [http://homepage.mac.com/drernie/plist.html plist] datatype mapping proposal
	* Revised [http://opendarwin.org/~drernie/xoxo-datatypes.html xoxo datatype] proposal		* Revised [http://opendarwin.org/~drernie/xoxo-datatypes.html xoxo datatype] proposal
			* HTML 5 [http://hsivonen.iki.fi/html5-datatypes/ datatypes]

	== See Also ==		== See Also ==
	* [[xoxo]]		* [[xoxo]]
	* [[naming-principles]]		* [[naming-principles]]

DrErnie: /* Usage */ clarify order independence

2006-03-31T17:52:02Z

Usage: clarify order independence

← Older revision		Revision as of 17:52, 31 March 2006
Line 117:		Line 117:
	== Usage ==		== Usage ==

	To indicate that a particular micforomat uses typed values, precede that microformat with the class name ''typed'', as in:		To indicate that a particular micforomat uses typed values, precede or follow that microformat with the class name ''typed'', as in:

	<pre><nowiki>		<pre><nowiki>
	<ol class=''typed xoxo''>		<ol class=''typed xoxo''>
	</nowiki></pre>		</nowiki></pre>

			or

			<pre><nowiki>
			<ol class=''xoxo typed''>
			</nowiki></pre>

			In other words, this defines what might be called the "<pre>typed</pre>" microformat.

	== Summary ==		== Summary ==

DrErnie: /* Summary */

2006-03-21T00:28:18Z

Summary

← Older revision		Revision as of 00:28, 21 March 2006
Line 123:		Line 123:
	</nowiki></pre>		</nowiki></pre>

	=== Summary ===		== Summary ==
	* string (optional)		* string (optional)
	* boolean (0,1)		* boolean (0,1)

DrErnie: /* Usage */

2006-03-21T00:28:00Z

Usage

← Older revision		Revision as of 00:28, 21 March 2006
Line 126:		Line 126:
	* string (optional)		* string (optional)
	* boolean (0,1)		* boolean (0,1)
	* int (MAY use long)		* int (WAS i4; MAY use long)
	* double		* double
	* datetime		* datetime (WAS dateTime.iso8601)
	* binary		* binary (WAS base64)
	* nil		* nil

DrErnie: /* Usage */

2006-03-21T00:26:58Z

Usage

← Older revision		Revision as of 00:26, 21 March 2006
Line 123:		Line 123:
	</nowiki></pre>		</nowiki></pre>

	=== ~~Tag~~ Summary ===		=== Summary ===
	* string (optional)		* string (optional)
			* boolean (0,1)
	* int (MAY use long)		* int (MAY use long)
	* ~~float~~		* double
	* datetime		* datetime
	* binary		* binary
			* nil

	== Example ==		== Example ==

DrErnie: /* Tag Summary */

2006-03-21T00:25:59Z

Tag Summary

← Older revision		Revision as of 00:25, 21 March 2006
Line 122:		Line 122:
	<ol class=''typed xoxo''>		<ol class=''typed xoxo''>
	</nowiki></pre>		</nowiki></pre>

			=== Tag Summary ===
			* string (optional)
			* int (MAY use long)
			* float
			* datetime
			* binary

	== Example ==		== Example ==

DrErnie: /* String */

2006-03-21T00:24:32Z

String

← Older revision		Revision as of 00:24, 21 March 2006
Line 114:		Line 114:
	* ''string'' MAY be omittted		* ''string'' MAY be omittted
	* thus, any unlabeled entries MUST be interpreted as strings.		* thus, any unlabeled entries MUST be interpreted as strings.

			== Usage ==

	To indicate that a particular micforomat uses typed values, precede that microformat with the class name ''typed'', as in:		To indicate that a particular micforomat uses typed values, precede that microformat with the class name ''typed'', as in:

DrErnie: /* Binary Data */

2006-03-21T00:24:04Z

Binary Data

← Older revision		Revision as of 00:24, 21 March 2006
Line 107:		Line 107:
	** at any rate, they MUST follow [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]		** at any rate, they MUST follow [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]
	** a more human-readable rendering may be used, with the ISO8601 value in an ''abbr''		** a more human-readable rendering may be used, with the ISO8601 value in an ''abbr''
	=== Binary Data ==		=== Binary Data ===
	* binary data SHOULD be encoded in a [http://en.wikipedia.org/wiki/Data:_URI_scheme data: URI], with an explicit [http://www.htmlhelp.com/reference/html40/special/a.html ContentType] and a human-readable description as the body of the anchor.		* binary data SHOULD be encoded in a [http://en.wikipedia.org/wiki/Data:_URI_scheme data: URI], with an explicit [http://www.htmlhelp.com/reference/html40/special/a.html ContentType] and a human-readable description as the body of the anchor.
	* therefore, use ''binary'' for ''base64'', as there may be alternate, non-base64 encodings in the future		* therefore, use ''binary'' for ''base64'', as there may be alternate, non-base64 encodings in the future

	=== String ===		=== String ===
	* ''string'' MAY be omittted		* ''string'' MAY be omittted

DrErnie: /* Proposal */ incorporate Kevin & Tantek's suggestions

2006-03-21T00:23:41Z

Proposal: incorporate Kevin & Tantek's suggestions

← Older revision		Revision as of 00:23, 21 March 2006
Line 94:		Line 94:
	== Proposal ==		== Proposal ==
	The proposal is to adopt [http://www.xmlrpc.com/spec/ XML-RPC] scalar values as the class names for typed microformats, with the following caveats:		The proposal is to adopt [http://www.xmlrpc.com/spec/ XML-RPC] scalar values as the class names for typed microformats, with the following caveats:
	* the alias 'i4' for integer SHOULD ~~not~~ be used		=== Integers ===
	* the name 'long' MAY be used for 64-bit or longer integers		* the alias ''i4'' for integer SHOULD NOT be used
	* ~~for~~ '~~dateTime~~'		* the name ''long'' MAY be used for 64-bit or longer integers
	** can we make this 'datetime' ~~? [[User:Kevin Marks\|Kevin Marks]] 16:39, 13 Feb 2006 (PST)~~		* thus, the name ''int'' MAY be used for more than 32-bit signed integers
	** ~~microformats don't use camel case. please see~~ [[naming-principles]]. ~~alternatives (Tantek):~~
	*** date-time (~~if you consider it to be two words~~)		=== Date and Time ===
	*** datetime (as proposed by Kevin, if you think it is one word)		* use ''datetime'' for ''dateTime.iso8601''
	~~***~~ dt (reusing the common prefix shared by existing microformat class names: dtstart, dtend, dtreviewed from [[hcalendar\|hCalendar]] and [[hreview\|hReview]]. We could also make that a [http://microformats.org/wiki/naming-principles#dt_properties general rule for microformat class names for properties which take ISO8601 datetimes]. (Tantek)		** camelCase is not appropriate according to microformat [[naming-principles]].
	** the trailing '.iso8601' MUST be omitted, as '.' is not (always?) valid in HTML class names		** '.' is neither a valid HTML class name, nor a valid character (unescaped at least) in a CSS class selector
	*** '.' is neither a valid HTML class name, nor a valid character (unescaped at least) in a CSS class selector. - Tantek		** Alternative: dt (reusing the common prefix shared by existing microformat class names: dtstart, dtend, dtreviewed from [[hcalendar\|hCalendar]] and [[hreview\|hReview]]. We could also make that a [http://microformats.org/wiki/naming-principles#dt_properties general rule for microformat class names for properties which take ISO8601 datetimes]. (Tantek)
	** date/time formats SHOULD follow the [http://www.w3.org/TR/NOTE-datetime W3C profile] of [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]		* date/time formats SHOULD follow the [http://www.w3.org/TR/NOTE-datetime W3C profile]
	** a more human-readable rendering may be used, with the ISO8601 value in an "abbr"		** at any rate, they MUST follow [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601]
			** a more human-readable rendering may be used, with the ISO8601 value in an ''abbr''
			=== Binary Data ==
	* binary data SHOULD be encoded in a [http://en.wikipedia.org/wiki/Data:_URI_scheme data: URI], with an explicit [http://www.htmlhelp.com/reference/html40/special/a.html ContentType] and a human-readable description as the body of the anchor.		* binary data SHOULD be encoded in a [http://en.wikipedia.org/wiki/Data:_URI_scheme data: URI], with an explicit [http://www.htmlhelp.com/reference/html40/special/a.html ContentType] and a human-readable description as the body of the anchor.
	* ~~if no datatype is specified~~, ~~an implementation MAY either attempt to infer a datatype from the syntax of the value~~, ~~or simply assert that the value is a string. Thus~~, ~~conforming implementations SHOULD always explicitly label strings.~~		* therefore, use ''binary'' for ''base64'', as there may be alternate, non-base64 encodings in the future
	** Disagree - ~~either we are labelling datatypes and thus labelling string is redundant, or we are trying to guess from syntax. If~~ the ~~latter this whole spec is unnecessary. [[User:Kevin Marks\|Kevin Marks]] 16:39, 13 Feb 2006 (PST)~~		=== String ===
	** Agreed with Kevin. Let'~~s keep~~ 'string' as ~~the default, and allow explicit usage of it~~. ~~-Tantek~~		* ''string'' MAY be omittted
			* thus, any unlabeled entries MUST be interpreted as strings.

	To indicate that a particular micforomat uses typed values, precede that microformat with the class name 'typed', as in:		To indicate that a particular micforomat uses typed values, precede that microformat with the class name ''typed'', as in:

	<pre><nowiki>		<pre><nowiki>
	<ol class="typed xoxo">		<ol class=''typed xoxo''>
	</nowiki></pre>		</nowiki></pre>