draft-ietf-appsawg-json-pointer-05.txt   draft-ietf-appsawg-json-pointer-06.txt 
Applications Area Working Group P. Bryan, Ed. Applications Area Working Group P. Bryan, Ed.
Internet-Draft Salesforce.com Internet-Draft Salesforce.com
Intended status: Informational K. Zyp Intended status: Informational K. Zyp
Expires: April 25, 2013 SitePen (USA) Expires: June 8, 2013 SitePen (USA)
M. Nottingham, Ed. M. Nottingham, Ed.
October 22, 2012 Akamai
December 5, 2012
JSON Pointer JSON Pointer
draft-ietf-appsawg-json-pointer-05 draft-ietf-appsawg-json-pointer-06
Abstract Abstract
JSON Pointer defines a string syntax for identifying a specific value JSON Pointer defines a string syntax for identifying a specific value
within a JSON document. within a JSON document.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 33 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 25, 2013. This Internet-Draft will expire on June 8, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 23 skipping to change at page 4, line 23
has the same number of Unicode characters as token and their code has the same number of Unicode characters as token and their code
points are position-wise equal. If a referenced member name is points are position-wise equal. If a referenced member name is
not unique in an object, the member that is referenced is not unique in an object, the member that is referenced is
undefined, and evaluation fails (see below). undefined, and evaluation fails (see below).
o If the currently referenced value is a JSON array, the reference o If the currently referenced value is a JSON array, the reference
token MUST contain either: token MUST contain either:
* characters that represent an unsigned base-10 integer value * characters that represent an unsigned base-10 integer value
(possibly with leading zeros), making the new referenced value (possibly with leading zeros), making the new referenced value
is the array element with the zero-based index identified by the array element with the zero-based index identified by the
the token, or token, or
* exactly the single character "-", making the new referenced * exactly the single character "-", making the new referenced
value the (non-existant) member after the last array element. value the (non-existant) member after the last array element.
If a reference token is being evaluated against a JSON document, If a reference token is being evaluated against a JSON document,
implementations will evaluate each token against the document's implementations will evaluate each token against the document's
contents, and terminate evaluation with an error condition if it contents, and terminate evaluation with an error condition if it
fails to resolve a concrete value for any of the JSON pointer's fails to resolve a concrete value for any of the JSON pointer's
reference tokens. See Section 7 for details. reference tokens. See Section 7 for details.
skipping to change at page 6, line 48 skipping to change at page 6, line 48
This document has no impact upon IANA. This document has no impact upon IANA.
9. Security Considerations 9. Security Considerations
A given JSON Pointer is not guaranteed to reference an actual JSON A given JSON Pointer is not guaranteed to reference an actual JSON
value. Implementations should be aware of this and take appropriate value. Implementations should be aware of this and take appropriate
precautions. precautions.
Note that JSON pointers can contain the NUL (Unicode U+0000) Note that JSON pointers can contain the NUL (Unicode U+0000)
character, which may not be representable in all programming character. Care is needed not to misinterpret this character in
languages. programming languages that use NUL to mark the end of a string.
10. Acknowledgements 10. Acknowledgements
The following individuals contributed ideas, feedback and wording to The following individuals contributed ideas, feedback and wording to
this specification: this specification:
Mike Acar, Carsten Bormann, Tim Bray, Jacob Davies, Martin J. Mike Acar, Carsten Bormann, Tim Bray, Jacob Davies, Martin J.
Duerst, Bjoern Hoehrmann, James H. Manger, Drew Perttula, Julian Duerst, Bjoern Hoehrmann, James H. Manger, Drew Perttula, Julian
Reschke. Reschke.
skipping to change at page 8, line 11 skipping to change at page 8, line 11
Phone: +1 604 783 1481 Phone: +1 604 783 1481
Email: pbryan@anode.ca Email: pbryan@anode.ca
Kris Zyp Kris Zyp
SitePen (USA) SitePen (USA)
Phone: +1 650 968 8787 Phone: +1 650 968 8787
Email: kris@sitepen.com Email: kris@sitepen.com
Mark Nottingham (editor) Mark Nottingham (editor)
Akamai
Email: mnot@mnot.net Email: mnot@mnot.net
 End of changes. 7 change blocks. 
8 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/