old-json-serializations - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:30:52Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:30, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~ufJSON or a Standard JSON Serialization for Microformats~~</entry-title>~~		{{DISPLAYTITLE:ufJSON or a Standard JSON Serialization for Microformats}}

	= Introduction =		= Introduction =

2012-10-25T17:51:14Z

json moved to old-json-serializations: Now out of date and obsoleted by canonical JSON as defined in microformats2

← Older revision	Revision as of 17:51, 25 October 2012
(No difference)

2010-07-04T22:21:03Z

wiki structure cleanup in preparation

2008-11-30T05:29:17Z

References: Added references to JSON-Schema and SOAPjr's DMD's

← Older revision		Revision as of 05:29, 30 November 2008
Line 277:		Line 277:
	*RFC 4627, current formal JSON specification.		*RFC 4627, current formal JSON specification.
	*[http://en.wikipedia.org/wiki/JSON JSON on Wikipedia]		*[http://en.wikipedia.org/wiki/JSON JSON on Wikipedia]
			*[http://json-schema.org/ JSON-Schema Proposal]
			*[http://soapjr.org/specs.html#dmd SOAPjr's Common DMD's (Data Model Definitions)]

2008-11-30T05:27:01Z

Envelope structure: Added reference to the SOAPjr - a hybrid of SOAP and JR (JSON-RPC)

← Older revision		Revision as of 05:27, 30 November 2008
Line 131:		Line 131:
	Each individual microformat data set can also have an optionally attached array		Each individual microformat data set can also have an optionally attached array
	of error messages where it is appropriate.		of error messages where it is appropriate.

			A new proposal that also addresses this area is [http://SOAPjr.org SOAPjr] - a hybrid of [http://en.wikipedia.org/wiki/SOAP_(protocol) SOAP] and [http://en.wikipedia.org/wiki/JSON-RPC JR (JSON-RPC)]. This adapts the SOAP/MIME Envelope/Head/Body separation into JSON.

	<pre>		<pre>
Line 269:		Line 271:
	}		}
	</pre>		</pre>



	==References==		==References==

2008-05-24T02:10:29Z

Authoring rules

2008-05-24T02:10:02Z

Authoring rules

← Older revision		Revision as of 02:10, 24 May 2008
Line 17:		Line 17:
	<pre>// Correct		<pre>// Correct
	"fn" : "John Doe",		"fn" : "John Doe",
	"n" : {,		"n" : {
	"given-name" : ["John"],		"given-name" : ["John"],
	"family-name" : ["Doe"]		"family-name" : ["Doe"]
Line 36:		Line 36:
	<pre>// Correct		<pre>// Correct
	"fn" : "John Doe",		"fn" : "John Doe",
	"n" : {,		"n" : {
	"given-name" : ["John"],		"given-name" : ["John"],
	"family-name" : ["Doe"]		"family-name" : ["Doe"]
Line 43:		Line 43:
	// Wrong - givenName has been camel cased, it should be given-name		// Wrong - givenName has been camel cased, it should be given-name
	"fn" : "John Doe",		"fn" : "John Doe",
	"n" : {,		"n" : {
	"givenName" : ["John"],		"givenName" : ["John"],
	"familyName" : ["Doe"]		"familyName" : ["Doe"]

2008-05-16T06:50:26Z

← Older revision		Revision as of 06:50, 16 May 2008
Line 74:		Line 74:
	* Escape JSON values where needed.		* Escape JSON values where needed.
	* This is a http://json.org syntax rule		* This is a http://json.org syntax rule
	** ~~The example below is wrong.~~ In JSON only the backslash, double quote and ASCII control characters need to be escaped. Forward slashes may be escaped, but do not have to be.		** In JSON only the backslash, double quote and ASCII control characters need to be escaped. Forward slashes may be escaped as in the URL example below, but do not have to be.

	<pre>		<pre>
	// Correct		// Correct
			"note" : [ "My current job title is \"Interactive Designer\"" ]

			// Wrong
			"note" : [ "My current job title is "Interactive Designer"" ]

			// Optional
	"url" : [ "http:\/\/www.joeblogs.com\/" ]		"url" : [ "http:\/\/www.joeblogs.com\/" ]

	~~// Wrong~~
	~~"url" : [ "http://www.joeblogs.com/" ]~~
	</pre>		</pre>

2008-05-11T20:06:31Z

← Older revision		Revision as of 20:06, 11 May 2008
Line 31:		Line 31:
	'''Use the same property names as microformat equivalents'''		'''Use the same property names as microformat equivalents'''
	* All property names must be consistent with their equivalent microformat name. They should '''not''' be camel cased.		* All property names must be consistent with their equivalent microformat name. They should '''not''' be camel cased.
	* All property names must be enclosed with double quotes to allow hyphenated properties.		* All property names must be enclosed with double quotes to allow hyphenated properties.
			** This is a JSON syntax rule anyway - do we need to restate it?

	<pre>// Correct		<pre>// Correct
Line 73:		Line 74:
	* Escape JSON values where needed.		* Escape JSON values where needed.
	* This is a http://json.org syntax rule		* This is a http://json.org syntax rule
			** The example below is wrong. In JSON only the backslash, double quote and ASCII control characters need to be escaped. Forward slashes may be escaped, but do not have to be.

	<pre>		<pre>

2008-05-10T16:27:12Z

← Older revision		Revision as of 16:27, 10 May 2008
Line 1:		Line 1:
			<div style="float:right;margin-left:1em">__TOC__</div>

	= Standardised microformats representation in JSON - ufJSON =		= Standardised microformats representation in JSON - ufJSON =