Re: [camp-comment] 1.8 Normative References, JSON Patch

[GILBERT PILZ <gilbert.pilz@oracle.com>]

Patrick,

Your comment relates to an existing issue, CAMP-54, and will be processed under that issue. As you can see from the comment thread, there was an approved motion to update the spec in the manner that you propose. However, there was an editorial error in processing this issue and this resolution did not appear in the PR draft. We will re-open the issue and process.

~ gp

On 9/4/2013 2:17 PM, Patrick Durusau wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

In 1.8 Normative References, JSON Patch is cited as:

*****
[JSON Patch] P. Bryan, M. Nottingham, “JSON Patch”, IETF Draft,
January 2013. http://tools.ietf.org/html/draft-ietf-appsawg-json-patch-10
*****

There are two issues.

First, draft work should never be used in normative references at all.
Under any circumstances. As the TC Process notes (Section 1, w:):

*****
"Normative Reference" means a reference in a Standards Track Work
Product to an external document or resource with which the implementer
must comply, in order to comply with a Normative Portion of the Work
Product.
*****

Note the "must comply" language.

Drafts by their very nature change and reliance on a draft invites a
lack of interoperability.

Second issue, fortunately this work is no long in draft but a final RFC.

The correct citation is:

*****
RFC6902 Bryan, P., Ed., and M. Nottingham, Ed., "_javascript_ Object
Notation (JSON) Patch", RFC 6902, April 2013.
*****

The canonical URL, in case you want to add it is:

http://www.rfc-editor.org/rfc/rfc6902.txt

On the status of a "draft standard" see:
http://www.rfc-editor.org/rfc/rfc2026.txt

Hope everyone is having a great day!

Patrick

- -- 
Patrick Durusau
patrick@durusau.net
Technical Advisory Board, OASIS (TAB)
Former Chair, V1 - US TAG to JTC 1/SC 34
Convener, JTC 1/SC 34/WG 3 (Topic Maps)
Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300
Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps)

Another Word For It (blog): http://tm.durusau.net
Homepage: http://www.durusau.net
Twitter: patrickDurusau
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSJ6NvAAoJEAudyeI2QFGoMwMQAIuwmZ62ogw8Q/4fGr5XQKyr
0LrB7pF8uXaVv0Myp8DA3NmEoOjuJvsHPg9PMsceUMhIHJ3GdOaxIS34okRHGzyI
A6Wx9BlM6/YNgucI5R93VF3hj+rNfFirlmAw1+XVFPqDsV6nOOXhfv6XsZau6ajS
ctoKL06Azzn3s4QwrifrBPmUO7VTWLjAQ7GVSldJ/cC+wN8ogzQliqPCjNuLhX+0
iS4+yanR4OM8a6N3oilVjX7Y1aKP02UOnRsIn1EOdqif5Qd/CrQLldYERzHAZq5D
7nm126HtZroNmbKVA1gIWDDmnNWR/J2mA+BptB35HJ2j9iKYBxZtTNbXIFACfHp8
JK0RZfGm4rVksezSCXtAOEksC/qnIAFHCXwfxmsaZFSdXkMPtp3s+t65S2F8ysQU
qb2By3P0DZUqJAXm0JK80Q8HS2C6jxyr+4Tvm3zajoz4UrMNkGI8xK61fpxn/7fX
XRQTM9qV11xDc5LXZ2bOq4dm42C2ckz91J0OKe+WlesbfsXGqLgJHovJ+kqcab6T
nLbMSU+nBst2AGdKHKICL0X6BJS0nqRoSCB0JTLDn81z9HZozQKFhEVgLE+xxkfr
k0qc0roFMhyIhEbYFIU/13DN2H0GG16UgVeWEH0eEQD2/3ZivXUBfMoFzgkdm38x
2u0YX/6SBq0EvpPkyfRV
=C76J
-----END PGP SIGNATURE-----

--

This publicly archived list offers a means to provide input to the

OASIS Cloud Application Management for Platforms (CAMP) TC.



In order to verify user consent to the Feedback License terms and

to minimize spam in the list archive, subscription is required

before posting.



Subscribe: camp-comment-subscribe@lists.oasis-open.org

Unsubscribe: camp-comment-unsubscribe@lists.oasis-open.org

List help: camp-comment-help@lists.oasis-open.org

List archive: http://lists.oasis-open.org/archives/camp-comment/

Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf

List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Committee: http://www.oasis-open.org/committees/camp

Join OASIS: http://www.oasis-open.org/join/