attachment-0002
<div dir="ltr"><div>Hi,<br><br></div>Relevant especially for Google Cloud Print collaboration.<br clear="all"><div><div><div><br></div>
Cheers,<br></div><div>- Ira<br><br></div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername"></b> <span dir="ltr"><<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>></span><br>
Date: Tue, Apr 2, 2013 at 8:36 PM<br>Subject: [apps-discuss] RFC 6901 on JavaScript Object Notation (JSON) Pointer<br>To: <a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a><br>
Cc: <a href="mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a>, <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br><br><br>A new Request for Comments is now available in online RFC libraries.<br>
<br>
<br>
RFC 6901<br>
<br>
Title: JavaScript Object Notation (JSON) Pointer<br>
Author: P. Bryan, Ed.,<br>
K. Zyp,<br>
M. Nottingham, Ed.<br>
Status: Standards Track<br>
Stream: IETF<br>
Date: April 2013<br>
Mailbox: <a href="mailto:pbryan@anode.ca">pbryan@anode.ca</a>,<br>
<a href="mailto:kris@sitepen.com">kris@sitepen.com</a>,<br>
<a href="mailto:mnot@mnot.net">mnot@mnot.net</a><br>
Pages: 8<br>
Characters: 13037<br>
Updates/Obsoletes/SeeAlso: None<br>
<br>
I-D Tag: draft-ietf-appsawg-json-pointer-09.txt<br>
<br>
URL: <a href="http://www.rfc-editor.org/rfc/rfc6901.txt" target="_blank">http://www.rfc-editor.org/rfc/rfc6901.txt</a><br>
<br>
JSON Pointer defines a string syntax for identifying a specific value<br>
within a JavaScript Object Notation (JSON) document.<br>
<br>
This document is a product of the Applications Area Working Group Working Group of the IETF.<br>
<br>
This is now a Proposed Standard.<br>
<br>
STANDARDS TRACK: This document specifies an Internet standards track<br>
protocol for the Internet community,and requests discussion and suggestions<br>
for improvements. Please refer to the current edition of the Internet<br>
Official Protocol Standards (STD 1) for the standardization state and<br>
status of this protocol. Distribution of this memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="http://www.ietf.org/mailman/listinfo/ietf-announce" target="_blank">http://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<a href="http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" target="_blank">http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="http://www.rfc-editor.org/rfcsearch.html" target="_blank">http://www.rfc-editor.org/rfcsearch.html</a>.<br>
For downloading RFCs, see <a href="http://www.rfc-editor.org/rfc.html" target="_blank">http://www.rfc-editor.org/rfc.html</a>.<br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
<br>
<br>
_______________________________________________<br>
apps-discuss mailing list<br>
<a href="mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/apps-discuss" target="_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</div><br></div></div></div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.