[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (EMIX-318) wd19 .doc: clearlydistinguish (and separate where possible) normative from non-normativeinformation
wd19 .doc: clearly distinguish (and separate where possible) normative from non-normative information ------------------------------------------------------------------------------------------------------ Key: EMIX-318 URL: http://tools.oasis-open.org/issues/browse/EMIX-318 Project: OASIS Energy Market Information Exchange (eMIX) TC Issue Type: Improvement Reporter: Anne Hendry Assignee: William Cox Lines 302-303 states "Information in the "Specification" column of the tables is normative. Information appearing in the note column is explanatory and non-normative." It would make the spec easier to use and remove ambiguity if the normative and non-normative information were not mixed together in sections, tables, and table cells. Any section would be best constructed to be either all 'normative' or all 'non-normative' and clearly labeled at the top of the section. Lines 302 - 303 can be removed once non-normative information (notes, etc) is removed from (normative?) tables. Line 304 "All sections explicitly noted as examples are informational and are not to be considered normative." I think this applies to more than the examples and we should label all sections that are non-normative, then can remove this sentence. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]