OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

camp-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [camp-comment] 1.8 Normative References, YAML 1.1


Since this issue is different in nature from your previous comments on normative references, I have created a separate Jira issue to track it: CAMP-86.

~ gp

On 9/4/2013 2:37 PM, Patrick Durusau wrote:
Hash: SHA1


I noticed the *normative* reference to YAML under 1.8 Normative

Not being familiar with it, I followed the link.

- From "Status of this Document" I read:

This specification is a draft reflecting consensus reached by members
of the yaml-core mailing list. Any questions regarding this draft
should be raised on this list. We expect all further changes to be
strictly limited to wording corrections and fixing production bugs.

So the YAML normative reference is to a draft dated 2005-01-18, that
reflects a "consensus" of members of a mailing list.

Is that a fair characterization?

There is no formal organization charged with its maintenance and no
known process other than email "consensus" as far as any changes?

As I said in a post earlier today:

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

Note the "must comply" language.

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

- From examining the draft it is clear that conformance to YAML, a
mailing list consensus draft, is critical for use of this standard.

The only solution that comes to mind, given that YAML states it can be
copied if not modified, would be to include a copy of YAML 1.1 as an
appendix and cite that appendix as your normative reference.

That fixes the text of YAML 1.1 to be what is included in the appendix
and provides implementers with a stable target for their implementations.

If YAML has not been modifed since its "final draft" date of
2005-01-18, it should be stable enough to not burden the TC with too
many maintenance duties.

Hope everyone is having a great day!


- -- 
Patrick Durusau
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
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/


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/

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]