[OASIS Issue Tracker] (WSCALENDAR-512) Normative text confusion

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

     [ https://issues.oasis-open.org/browse/WSCALENDAR-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Cox updated WSCALENDAR-512:
-----------------------------------

    Resolution: 
 Revise to have one statement in one location of normative versus non-normative; reference line 72 (Section 1.6, Editing Conventions) at line 2 as follows:

All text is normative unless otherwise labeled. Notes and examples are non-normative; see Section 1.6 Editing Conventions.

  was:
 Revise to have one statement in one location of normative versus non-normative (see lines 2, 70-72, and combine at line 2).

Consider wording such as "notes and examples are always non-normative." Other text is normative unless labeled as non-normative.


> Normative text confusion
> ------------------------
>
>                 Key: WSCALENDAR-512
>                 URL: https://issues.oasis-open.org/browse/WSCALENDAR-512
>             Project: OASIS Web Services Calendar (WS-Calendar) TC
>          Issue Type: Bug
>          Components: PIM
>    Affects Versions: PIM CSPRD02
>         Environment: TAB Comments. Line 2, 70-72
>            Reporter: Toby Considine
>            Assignee: William Cox
>             Fix For: PIM WD11
>
>
> Section 1 reads: ***** All text is normative unless otherwise labeled. ***** However, that is contradicted by 1.6, which reads in part: ***** All items in the tables not marked as “optional” are mandatory. Information in the “Specification” column of the tables is normative. Information appearing in the “Note” column is explanatory and non-normative. All sections explicitly noted as examples are informational and are not to be considered normative. ***** So information in the Note column, if not labeled as non-normative is normative, except that if it is in the Note column then it is explanatory. Yes? This type of conflict/confusion is unnecessary.



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