A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Validator.nu JSON Output: Difference between revisions
| Line 16: | Line 16: | ||
A message ''object'' has one mandatory key, <code>"class"</code>, and seven optional keys, <code>"type"</code>, <code>"message"</code>, <code>"extract"</code>, <code>"extract-offset"</code>, <code>"url"</code>, <code>"line"</code> and <code>"column"</code>. | A message ''object'' has one mandatory key, <code>"class"</code>, and seven optional keys, <code>"type"</code>, <code>"message"</code>, <code>"extract"</code>, <code>"extract-offset"</code>, <code>"url"</code>, <code>"line"</code> and <code>"column"</code>. | ||
=====The <code>"class"</code> ''string''===== | |||
The <code>"class"</code> ''string'' denotes the general class of the message. The permissible values are <code>"info"</code>, <code>"error"</code> and <code>"non-document-error"</code>. | |||
The <CODE>"info"</CODE> | |||
means an informational message or warning that does not affect the validity of | |||
the document being checked. <CODE>"error"</CODE> signifies | |||
a problem that causes the validation/checking to fail. <CODE>"non-document-error"</CODE> | |||
signifies an error that causes the checking to end in an indeterminate state because | |||
the document being validated could not be examined to the end. Examples of such errors include broken schemas, bugs in the validator and IO errors. (Note that when a schema has parse errors, they are first reported as <CODE>error</CODE>s and then a catch-all <CODE>non-document-error</CODE> is also emitted.) | |||
=====The <code>"type"</code> ''string''===== | |||
===The <code>"url"</code> ''string''=== | ===The <code>"url"</code> ''string''=== | ||
Revision as of 16:55, 11 September 2007
This is a draft of a Web service response format for Validator.nu for clients that prefer JSON over XML.
Italicized words, such as object, refer to JSON data types.
Root Object
The root object is a JSON object. It has two mandatory keys, "messages" and "result", and three optional keys, "url", "source" and "parse-tree".
The values for these keys are described below.
The "messages" array
The this array is an ordered collection of zero or more message objects.
Message objects
A message object has one mandatory key, "class", and seven optional keys, "type", "message", "extract", "extract-offset", "url", "line" and "column".
The "class" string
The "class" string denotes the general class of the message. The permissible values are "info", "error" and "non-document-error".
The "info"
means an informational message or warning that does not affect the validity of
the document being checked. "error" signifies
a problem that causes the validation/checking to fail. "non-document-error"
signifies an error that causes the checking to end in an indeterminate state because
the document being validated could not be examined to the end. Examples of such errors include broken schemas, bugs in the validator and IO errors. (Note that when a schema has parse errors, they are first reported as errors and then a catch-all non-document-error is also emitted.)