[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [obix] Minor items noted during production of your CSs
We had multiple conversations about the Namespace prior to public review. I’m glad they were found now, and we asked the TC Admins to fix prior to publication. Authorization to do so was specifically authorized in our vote.
The encodings should all use the latest namespace. Again, as authorized in the vote.
COAP upgrade is a nice catch. If asked as requested, we would have moved from draft to final
Acme to example is an agreeable change. No Anvils required.
As you have now published before resolving, or perhaps did not do the checking before publishing final review, we will need to make a vote on Non-significant corrections after the publication.
Would you advise on the proper procedures for that? DO we need another special majority vote?
“It is the theory that decides what can be observed."
Information Technology Services
University of North Carolina
Chapel Hill, NC
Chair, OASIS OBIX Technical Committee
Chair, OASIS WS-Calendar Technical Committee
Editor, OASIS EMIX, Energy Interoperation TC
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Chet Ensign
Sent: Tuesday, October 6, 2015 5:25 PM
Cc: Paul Knight <firstname.lastname@example.org>
Subject: [obix] Minor items noted during production of your CSs
Members of the OBIX TC,
While publishing your new Committee Specifications, we noted the following issues that you may wish to address at the next publication cycle.
- OBIX v1.1
The W3C link checker found a broken link to local resource hyperlinked to the word "OASIS" in the Non-Normative reference to "CamelCase". This should be removed.
Also, the links below are not broken, but the document does not use the exact URL, and the links are redirected. It may be a good idea to link to the final location, for the sake of speed.
Status: 301 -> 200 OK
The link is missing a trailing slash, and caused a redirect. Adding the trailing slash would speed up browsing.
Status: 301 -> 200 OK
The link is also missing a trailing slash, and caused a redirect. Adding the trailing slash would speed up browsing.
- Encodings for OBIX: Common Encodings Version 1.0
We noted that the Section 2.6 discussion of namespaces uses "http://docs.oasis-open.org/obix/ns/201410/def" instead of either http://docs.oasis-open.org/obix/ns/201410/schema (as defined in Section 2.5) or http://docs.oasis-open.org/obix/ns/201506/schema (as currently defined for OBIX v1.1 (csd04/csprd04/cs01)). You may want to check to see if this is correct.
- Bindings for OBIX: REST Bindings Version 1.0
In the Non-Normative references, the CoAP reference should cite the RFC instead of Internet draft.
The Pinger link check found a broken link for tje non-normative reference to CoAP-OBSERVE. It looks like the Internet draft cited has expired. The TC should update the reference.
- Bindings for OBIX: SOAP Bindings Version 1.0
Please let us know if you have any questions on these.