Changes

Jump to navigation Jump to search
23 bytes removed ,  17:00, 14 August 2011
# The resulting document has a <code><json/></code> root node.
# JSON keys are represented as elements:
## Empty keys are represented with an underscore (_). Values and values of arrays (which have no keys) will also be enclosed are represented by a single underscore tag names<code>&lt;_&gt;...&lt;/_&gt;</code>). ## Underscores in the key are represented with rewritten to two underscores (<code> __</code>). ## Spaces are represented with two underscores (___) ## Characters A character that cannot be represented as NCName character are represented with a leading and trailing is rewritten to an underscore and a its four-digit Unicode.# JSON values are represented as text nodes. # The types of value values are represented in attributes: ## The value types ''number'', ''boolean'', ''null '', ''object'' and ''array '' are represented with by a <code>type </code> attribute. ## String and object types are The ''string'' type is omitted , as they are it is treated as default types for flat elements and and nested elements with/without namestype. ## If a key has the same type throughout the whole document, the type attribute will be omitted. Instead, the key will be listed in additional, type-specific attributes in the root node. The attributes are named by their type (''number'', ''boolean'', ''null '', ''object'' or ''array'') and will contain all relevant keys as value, separated by whitespaces.
|-
| valign='top' | '''Errors'''
Bureaucrats, editor, reviewer, Administrators
13,550

edits

Navigation menu