RE: [obix] Groups - oBIXfigure1UML.png uploaded

We did much the same in WS-Calendar.

 

WS-Calendar type pre-dated XML types.

 

Some had particular pattern expectations.

 

See the WS-Calendar artifacts linked from the namespace document at:

 

http://docs.oasis-open.org/ns/ws-calendar

 

Go down to the CS01 Schemas.

 

All types are defined in the valtypes  schema (which look exactly like what Craig is describing) then look at props to see how we use them.

 

WS-Calendar required extensive use of substitution groups to align with pre-existing work in the IETF; oBIX will not need to be so complex. Still. If we define
 low level elements as we did in the valtypes schema, then we can put restrictions, patterns, etc, and this becomes a normative description for all encodings, even if they do not use XML (if we so declare).

 

 

ALSO:

 

Note the namespace document named above (http://docs.oasis-open.org/ns/ws-calendar) which is in RDDL
 (Resource Directory Description Language) (http://www.rddl.org/) which provides both a machine and human readable guide to the XML artifacts.

 

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:  [mailto:]
On Behalf Of Gemmill, Craig

Sent: Wednesday, May 08, 2013 12:51 PM

To: Chris Bogen; 

Subject: RE: [obix] Groups - oBIXfigure1UML.png uploaded

 

One thing I would rather see is these things defined in terms of their oBIX constructs, instead of the xsd types.  Maybe this is what 1) is about, but it would
 seem more self consistent if, for example, the ‘name’ attribute were an obix:str, instead of an xs:string.  Even though obix:str maps to an xs:string, the name is really an obix:str and the fact that the two are the same is sort of a coincidence of the way
 we defined obix:str.  Is it somehow invalid UML to have it be an obix:str instead of xs:string?  I’m not an expert at UML.

 

I can easily embed this into the doc once we agree on whether this is ok.

 

 

 

From:
 [mailto:]
On Behalf Of Chris Bogen

Sent: Tuesday, May 07, 2013 4:02 PM

To: 

Subject: [obix] Groups - oBIXfigure1UML.png uploaded

 

Submitter's message

I uploaded a draft version of a new Figure 1 for the next working draft. I can arrange it to look better in the final version, but wanted to get feedback first.

My goal was to represent the object model in UML class diagram notation, but with a little more detail. As it currently exists Figure 1 is technically a very simple UML class diagram. Major changes:

1) I added namespace/package prefixes to distinguish between oBIX and native or xsd mapped types. As it is the diagram is ambiguous.

2) Represented "val" as a proper parameterized class with type binding relations from subclasses.

3) Added the "status" enumeration for clarification.

There are some issues that I found while making the diagram, such as...

a) why does int use a uri for units while date uses a string?

b) In facets there is discussion about using tz in abstime, date, or time, but in the current Figure 1, tz is not an attribute of those classes.

c) related to b, why doesn't reltime have units?

Regards,

Chris 

-- Chris Bogen 

Document Name:

oBIXfigure1UML.png

Description

A draft revision of the oBIX Figure 1 illustration 

Download Latest Revision

Public Download Link

Submitter: Chris Bogen

Group: OASIS Open Building Information Exchange (oBIX) TC

Folder: Contributions

Date submitted: 2013-05-07 13:01:51