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

 


Help: OASIS Mailing Lists Help | MarkMail Help

obix message

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


Subject: [OASIS Issue Tracker] Commented: (OBIX-162) 17 Conformance


    [ http://tools.oasis-open.org/issues/browse/OBIX-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36803#action_36803 ] 

Craig Gemmill  commented on OBIX-162:
-------------------------------------

I've simply removed the sentence in 17 describing the precedence, allowing the normal order to exist.  I think that clears up the conflict.

Question: where to reference the schema doc - in the normative references section?  It appears the header boilerplate already references the location in the "Additional artifacts" section, but only to the directory, not the actual .xsd file.


> 17 Conformance
> --------------
>
>                 Key: OBIX-162
>                 URL: http://tools.oasis-open.org/issues/browse/OBIX-162
>             Project: OASIS Open Building Information Exchange (oBIX) TC
>          Issue Type: Bug
>          Components: OBIX 1.1 Specification
>    Affects Versions: OBIX 1.1 PR02
>         Environment: TAB Review
>            Reporter: Toby Considine
>            Assignee: Craig Gemmill 
>            Priority: Critical
>
> "17 Conformance reads in part: 
> ***** 
> An implementation is conformant with this specification if it satisfies all of the MUST and REQUIRED level requirements defined herein for the functions implemented. Normative text within this specification takes precedence over normative outlines, which in turn take precedence over the XML Schema and WSDL descriptions, which in turn take precedence over examples. 
> ***** 
> Possibly my mis-reading but this prose appears to contradict the statements in 1.6 that read in part: 
> ***** 
> All sections explicitly noted as examples are informational and SHALL NOT be considered normative. 
> All UML and figures are illustrative and SHALL NOT be considered normative. 
> ***** 
> I read this prose in 17 as making examples, UML and figures normative. Yes? 
> BTW, the conformance clause does not mention http://docs.oasis-open.org/obix/obix/v1.1/csprd02/schemas/obix-v1.1.xsd 
> The TC Process, https://www.oasis-open.org/policies-guidelines/tc-process, provides at (7a) third unnumbered bullet point that: 
> ***** 
> Where any definition in these separate files disagrees with the definition found in the specification, the definition in the separate file prevails. 
> ***** 
> I realize that your ""...take precedence over the XML Schema and WSDL descriptions"" does not contradict that rule but it would be best to include the separate computer files (the XML schema and the RDDL file) as part of the conformance clause. Just to remove any ambiguity."

-- 
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]