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] Should? or Must? re: conformance

Hi Craig, 

Just commenting for OASIS, there are no rules about how we like or expect things done beyond the simple requirement that the spec have " a separate section, listing a set of numbered conformance clauses, to which any implementation of the specification must adhere in order to claim conformance to the specification (or any optional portion thereof)." 

The TAB put together guidelines to help with writing conformance clauses and you can access that at http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html .  They are revisiting and updating it now but it is still a good basis for working. 


On Fri, Dec 6, 2013 at 6:26 AM, Gemmill, Craig <craig.gemmill@tridium.com> wrote:

As I started to write the conformance language for Section 17 based on our discussion from yesterday, I talked myself into a corner on this.  I’d appreciate some input from those familiar with OASIS rules about conformance, etc. and how they like things done.


I think our desire is:

·         for 1.1 and greater, the models, encodings, and bindings sections of the Lobby are REQUIRED

·         for 1.0, they are obviously not required, as no 1.0 server would ever have them

·         a 1.1 client should be able to handle the absence of these properties when talking to a 1.0 server

·         we want to maintain the backwards compatibility


So is the way to do this:

a)      make the properties have ‘null=”true” ‘ in the schema for the contract?  Or

b)      make the properties not be null – thus indicating they are required – but include a statement in the spec that clients must be able to handle the nonexistence of the properties?


I think we’ve been following a) so far, but perhaps b) makes better sense?  Because we DON’T want to suggest that a person implementing a 1.1 server can just decide not to have the properties, that defeats the purpose of having them!  My thought would be to take the null default off of the properties, and add language to Section 5 about the new properties, saying that clients should expect to handle them not being there for backwards compatibility.  Also probably put something into 17 somewhere that clients must be able to handle nonexistence of newer properties for this reason.


Any suggestions?




Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open

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