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] Groups - obix-v1.1-wd37-noXsd.zip uploaded


Most of these are trivial. One (IS and friends) needs consensus.

 

The only important one, and I think we touched on it in the call, is the one about the is, in, of, and out attributes.  These are not of type “contract”, they are of type “contract list”, which is a space-separated list of one or more contracts.  Unless “contract” is defined as that?

 

1)      It could be of type obix:List, and be conformed to only contracts

2)      It could be a set of 1-many contract objects

3)      Alternately, a single object could have multiple IS object, but one element have multiple instances of the same attribute strikes me as bad practice.

 

I think Craig has suggested (1), but if (2) is non-breaking, it strikes me as a better solution.

 

tc

 

 


"There are seldom good technological solutions to behavioral problems."

-- Ed Crowley


Toby Considine
TC9, Inc.

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

http://www.tc9.com

  

Chair, OASIS OBIX Technical Committee

Chair, OASIS WS-Calendar Technical Committee

Editor, OASIS Energy Market Information Exchange (EMIX)
Editor, OASIS Energy Interoperation
blog: http://www.NewDaedalus.com 

 

 

From: Gemmill, Craig [mailto:craig.gemmill@tridium.com]
Sent: Wednesday, October 29, 2014 9:48 AM
To: William Cox; obix@lists.oasis-open.org; Toby Considine
Subject: RE: [obix] Groups - obix-v1.1-wd37-noXsd.zip uploaded

 

Yep – I saw it, and I’ve made a few comments to Toby on it.  I’ll include those here, if it helps.

 

A couple comments on the xsd:

·         nit: line 74: oBIX -> OBIX

·         nit: line 12: elment -> element

·         nit: line 15: validitiy -> validity

·         line 221: If the ‘is’ attribute defines the contracts implemented by the object, should it be a contract list rather than just a contract?  This also applies to in, of, and out, according to Section 7.2.

·         nit: line 354: oBIX -> OBIX

 

 

The only important one, and I think we touched on it in the call, is the one about the is, in, of, and out attributes.  These are not of type “contract”, they are of type “contract list”, which is a space-separated list of one or more contracts.  Unless “contract” is defined as that?

 

 

 

From: William Cox [mailto:wtcox@CoxSoftwareArchitects.com]
Sent: Wednesday, October 29, 2014 9:40 AM
To: obix@lists.oasis-open.org; Gemmill, Craig; Toby Considine
Subject: Re: [obix] Groups - obix-v1.1-wd37-noXsd.zip uploaded

 

Craig -

Toby had posted a "wd36.1" for review on 27 October or so - notice sent to the list.

I think that's the one to include.

Thanks!

bill

On 10/29/14 8:15 AM, Craig Gemmill wrote:

Submitter's message
Hi all-

Here is the meat of WD37, the spec doc in Word and PDF format. It contains the changes we discussed in the TC call last week as well as over email this week. I did not have the WD37 XSD file. If the WD36 XSD is fine, I will rename it to WD37 and submit a formal WD37 doc, but this is fine to read in the meantime, so we can be prepared to vote on it Thursday.

Craig

-- Mr. Craig Gemmill

Document Name: obix-v1.1-wd37-noXsd.zip


Description
WD37 document with changes discussed in TC call 10/23 plus over email,
without associated XSD.
Download Latest Revision
Public Download Link


Submitter: Mr. Craig Gemmill
Group: OASIS Open Building Information Exchange (oBIX) TC
Folder: Standards
Date submitted: 2014-10-28 17:15:30

 



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