[OASIS Issue Tracker] (WSCALENDAR-516) Four (4) incorrect RFC citations

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/WSCALENDAR-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41740#comment-41740 ] 

William Cox commented on WSCALENDAR-516:
----------------------------------------

On attempting to apply the resolution there are several difficulties.

(1) The IETF format is recommended, not controlling; I cannot locate OASIS citation formats except for those in the "recommended citation" and the starter documents. The major item missing is the classification of the RFC, e.g. STD for standards track and approved.

(2) The IETF format is "consistently inconsistent" with all but the final author IF MORE THAN ONE as <lastname>, <first initial or initials>.

(3) TC Admin should resolve this issue of format. At least for RFC2119, TC Admin says that documents not following the starter document will be rejected. TC Admin is silent on reference format otherwise so far as I can find, except for the recommended format for citation of OASIS documents.

(4) For me this is a profound "don't care, I'll follow TC Admin's guidance"

Suggested solution:

TC Admin decides what format to use for RFC2119, and all other RFC citations follow that format.  (I suggest
                [RFC2119]               Bradner, S., Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, BCP 14, IETF RFC 2119, March 1997.
with the title in Italic rather than in double quotes which don't belong in text style supporting documents. "BCP 14" is not present and "S. Bradner" is the author name used in the starter document.


> Four (4) incorrect RFC citations
> --------------------------------
>
>                 Key: WSCALENDAR-516
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-516
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Bug
>          Components: PIM
>    Affects Versions: PIM CSPRD02
>         Environment: TAB Comments
>            Reporter: Toby Considine
>            Assignee: William Cox
>            Priority: Minor
>             Fix For: PIM WD11
>
>
> All four (4) of the RFCs in 1.2 Normative References are cited incorrectly. That includes 2219, which is properly cited in the template distributed by the TC admin.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)