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: RE: [obix] Specification Cross References

And each will get a new document ID at each upload.

And the links will be out of date with each upload.


In the motions, published earlier today, it says 4 times:


We further direct that the references in the specification be aligned so that each references the other properly:

•             oBIX Version 1.1 CSD 01

•             Encodings for OBIX: Common Encodings Version 1.0 CSD 01

•             OBIX: REST Bindings Version 1.0 CSD 01

•             Bindings for OBIX: SOAP Bindings Version 1.0 CSD01



CSD01 is the Committee Specification Draft, which is created through the motions.




"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


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



From: obix@lists.oasis-open.org [mailto:obix@lists.oasis-open.org] On Behalf Of Markus Jung
Sent: Tuesday, July 09, 2013 8:26 PM
To: obix@lists.oasis-open.org
Subject: Re: [obix] Specification Cross References



I have seen that the cross references in the latest doc are slightly out dated and some are not correct.

For example the REST bindings document does not correctly reference the Core and the the latest encoding working draft.

This should be normalized across all documents and corrected before we go out for PR. Should I do this today or do you like to do the final polishing?

Regarding the cross references, should we reference a certain working draft with a date or just include a general reference only to final committee specification with a month or without any date.  Because as soon all documents are approved they will be specifications and not working drafts any more.

For example we can reference the documents in the following ways

oBIX REST Bindings for OBIX: REST Bindings Version 1.0, 28 June 2013. OASIS Committee Specification Working Draft 06

or just:

oBIX REST Bindings for OBIX: REST Bindings Version 1.0, July 2013 OASIS Committee Specification

or even without a date:

oBIX REST Bindings for OBIX: REST Bindings Version 1.0,  OASIS Committee Specification

Most important is the version number. So I think the latest way is the most stable one.

Just let me know what you prefer and if you will update the references or I should do it.


Am 09.07.2013 02:40, schrieb Toby Considine:

The only issue I see is that we need to update the cross references between the specs before PR.


I can do that this evening, if folks want, or the respective editors people can do it themselves.




"Energy and persistence conquer all things." -- Benjamin Franklin

Toby Considine
TC9, Inc

OASIS TC Chair: oBIX & WS-Calendar

OASIS TC Editor: EMIX, Energy Interoperation

SGIP Smart Grid Architecture Committee


Email: Toby.Considine@gmail.com
Phone: (919)619-2104

blog: http://www.NewDaedalus.com


Dipl.-Ing. Markus Jung
Research Assistant
Tel. +43 1 58801-18322
Fax +43 1 58801-18391
Institute of Computer Aided Automation
Treitlstr. 1-3/4. Stock/E183-1
Vienna University of Technology

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