Sounds like we should proceed as Markus suggested post haste to clean up the conformance issues.
Other thoughts:
The first Public Review takes a minimum of 30 days. The TC MAY ask for longer.
Subsequent Public Reviews can be as short as 15 days.
1.1
is a new work product, so *that* PR WILL take at least 30 days
To me , the question is can we get PRs for the encodings and bindings out before the PR for 1.1 is done. I think we can.
tc
"When one door closes, another opens; but we often look so long and so regretfully upon the closed door that we do not see the one which has opened for us."
-- Alexander Graham Bell
Toby Considine
Chair, OASIS oBIX TC
Editor, OASIS EMIX, Energy Interoperation
Campus Services Information Technology
University of North Carolina
Chapel Hill, NC
|
|
Email:
Toby.Considine@ unc.edu
Phone: (919)962-9073
http://www.oasis-open.org
http://www.NewDaedalus.com
|
From: obix@lists.oasis-open.org [mailto:obix@lists.oasis-open.org]
On Behalf Of Bogen, Chris ERDC-RDE-ITL-MS
Sent: Tuesday, March 26, 2013 10:50 AM
To: obix@lists.oasis-open.org
Subject: [obix] Checking Conformance Clauses (UNCLASSIFIED)
Classification: UNCLASSIFIED
Caveats: FOUO
I reviewed the OASIS Conformance Guidelines (http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html#_Toc170119665)
and have provided my response to checklist items in bullets under the numbered checklist items.
Conformance Checklist
-
Are you using the right keywords from RFC 2119, and in uppercase?
-
If you are using ISO keywords, have you explicitly stated this in the specification ?
-
Have you defined your Conformance Target(s)?
-
Yes – implicit through statements of “conforming oBIX Client” or “conforming oBIX server”
-
Are all Normative Statements clearly identifiable?
-
Are all Normative Statements understandable, clear, and concise?
-
YES with one exception (20.1.2 (line 2699) “An implementation MUST return values according to the rules defined in Clause 4. “ Where is Clause 4?)
-
Are all Normative Statements referenced directly or indirectly from a Conformance Clause?
-
Yes, but recommend numbering the normative statements in each conformance clause section and providing a one sentence introduction before the normative statements (e.g. The oBIX server
MUST meet the following conditions to satisfy the Lobby Conformance Clause:…)
-
Note: A Normative Statement that is not related to any Conformance Clause has no meaning
-
Is each Normative Statement related to a Conformance Target(s)?
-
Yes, they are in sub-sections of conformance clauses
-
Is there a separate section containing the Conformance Clauses?
-
Yes, Section 20.1 and 20.2
-
Are all Conformance Clauses clearly identifiable?
-
Yes, there are subsections for each conformance clause. Though they are not explicitly identified as “Conformance Clauses,” the symbolism is implicit
-
Are all Conformance Clauses understandable, clear, and concise?
-
Are the top-level Conformance Clauses clearly identified and related to a Conformance Target?
-
Is the relationship between all Conformance Clauses clearly defined using combinations of combined, alternative, level and profile styles?
-
Are all Conformance Clauses either top-level or referenced directly or indirectly from a top-level Conformance Clause?
-
Implicity, yes, through statements such as “An implementation conforms to this specification as an oBIX Server if it meets the conditions described in the following subsections.” It is
recommended that “the following subsections) be directly referenced (e.g. …the conditions described in Sections 20.1.1, 20.1.2, and 20.1.3)
-
Note: A Conformance Clause that is not related to any top-level Conformance Clause has no meaning.
-
Are there any contradictions between Normative Statements on the one hand and a Conformance Clause and any referenced Conformance Clauses on the other hand? If there are, have these been explicitly
noted and have any rules to over-ride the contradictions been made
-
It depends on what encodings we include in 1.1. The statement, “An implementation SHOULD support the XML encoding,” (lines 2694-2695 and 2709-2709) may be invalid if there
are no other alternatives in which case the implementation MUST support the XML encoding
Chris Bogen, Ph.D.
Computer Scientist
US Army Corps of Engineers
Engineer Research Development Center
Vicksburg, MS
Classification: UNCLASSIFIED
Caveats: FOUO