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


Help: OASIS Mailing Lists Help | MarkMail Help

coel message

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

Subject: [OASIS Issue Tracker] (COEL-150) Clarify normative/non-normative content

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

Paul Bruton commented on COEL-150:

Perhaps we should mark these as non-normative, just for clarity (I think 10.1.1 for example should be clearly marked as n-n : or maybe it should be moved to COEL by Example?)

Should we reference any other targets in the conformance section (e.g. Personal Data Store, Personal Electronic device....) that we list in non-normative section 1.3?

> Clarify normative/non-normative content
> ---------------------------------------
>                 Key: COEL-150
>                 URL: https://issues.oasis-open.org/browse/COEL-150
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: Bug
>            Reporter: Paul Bruton
>            Assignee: Joss Langford
>              Labels: conformance
> Section 1.4: Clarify how normative and non-normative text is presented in the document. Specifically:	If a section is marked non-normative then all subsections are also non-normative.
> Make sure there is a  conformance clause referring to all sections that are normative.

This message was sent by Atlassian JIRA

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