RE: [obix] Groups - obix-v1.1-wd19.pdf uploaded

All-

 

I’ve made the watch changes (#1 below) to WD20, which I can post later today.

I’ve also made the corresponding changes to stdlib.obix, in case that is still important, or if the schema author wants to use it.  Will post along with WD20.

 

My question is about #5.  I see 1.1 as standing alone, because the references to the REST, SOAP, and Encodings docs are non-normative.  It seems to make the
 document more understandable to have these references in place, because it helps motivate the rules, and to give the reader a better sense of the “big picture”.  Are we sure we’d like to remove them?

If I can get feedback on that soon, I’d prefer to make the changes then post in WD20.  If I don’t hear anything I’ll just post it as is.

 

Thanks

Craig

 

 

 

From: Toby Considine [mailto:]
On Behalf Of Toby Considine

Sent: Monday, December 02, 2013 5:12 PM

To: Gemmill, Craig; 

Subject: RE: [obix] Groups - obix-v1.1-wd19.pdf uploaded

 

OK, thanks. So much for reviews on a phone…

 

Before next PR, we need:

 

1.1

 

1)     
Watch changes a indicated by Craig

2)     
Changes to Schema to support (1)

3)     
Additions to Schema to replace role of STDLIB.

4)     
Do we need UML to represent the LOBBY additions? STDLIB? Including this might improve document clarity.

5)     
OBIX Encodings, OBIX REST and OBIX SOAP should be removed from the non-normative references. Alternately, OBIX Web Sockets should be added. My concern
 here is that 1.1 should stand alone with no “circular’ references, 

 

Encodings:

 

6)     
For each encoding section, the mimetype used must be declared as described in Declarations of Binding type as described in 5.4.2. I.e., for each encoding,
 there should be a section that states “The mime type for this encoding is xxx”.  

 

Binding SOAP

 

7)     
There should be a section that indicates binding as described in section 5.4.3, i.e., the name “SOAP”, and the displayName “soapBinding”. The val,
 of course, is the current version of the document.

8)     
Are any WSDL changes to support the Lobby changes?

 

Binding REST

 

9)     
There should be a section that indicates binding as described in section 5.4.3, i.e., the name “REST”, and the displayName “restBinding”. The val,
 of course, is the current version of the document.

 

Binding WebSockets

 

10)  
There should be a section that indicates binding as described in section 5.4.3, i.e., the name “WS” (or other), and the displayName “webSockets”.
 The val, of course, is the current version of the document.

11)  
Once (1) is complete, the portions that describe the watch should be reviewed, and probably removed, to avoid potential redefinition and/or conflict
 with the core specification.

 

Any other issues remaining?

 

I am 13 timezones away from my normal one this week, and may not be able to make the meeting, but I will try. I have a new-found respect for those who have
 participated from Asia.

 

tc

"If something is not worth doing, it`s not worth doing well "    -- Peter Drucker

Toby Considine

TC9, Inc

OASIS TC Chair: oBIX & WS-Calendar

OASIS TC Editor: EMIX, Energy Interoperation

SGIP Smart Grid Architecture Committee

  

Email:



Phone: (919)619-2104

http://www.tcnine.com

blog: http://www.NewDaedalus.com 

 

From: Gemmill, Craig [mailto:]

Sent: Monday, December 02, 2013 10:34 PM

To: Considine, Toby; 

Subject: RE: [obix] Groups - obix-v1.1-wd19.pdf uploaded

 

Toby-

                                                                                  

I don’t have the watch changes needed by websockets (unsolicitedBufferDelay, maxBufferedEvents, etc.) in the core for WD19, just the description tweaks that
 we discussed in the last TC meeting.  I think the plan was to move these into the core, which I can try to get in before this week’s meeting.

 

Craig

 

 

From:
 [mailto:]
On Behalf Of Considine, Toby

Sent: Friday, November 29, 2013 11:04 AM

To: Gemmill, Craig; 

Subject: RE: [obix] Groups - obix-v1.1-wd19.pdf uploaded

 

This looks pretty good. I think we are getting there.

 

I recommend that members review this as if it is a candidate for Public Review.

 

Matthias:

 

With the watch information now in the core, can we abbreviate that watch in Web Sockets to avoid re-statement?

 

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

Finance & Administration IT

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 Craig Gemmill

Sent: Tuesday, November 26, 2013 2:44 PM

To: 

Subject: [obix] Groups - obix-v1.1-wd19.pdf uploaded

 

Submitter's message

Just in time for Thanksgiving, here is Working Draft 19. If the tryptophan in the turkey doesn't put you to sleep, this will!

OBIX Specification v1.1, Working Draft 19

* Reworked Section 5.4, Models/Encodings/Bindings

* Added versioning section

* Minor update to Watch language to move semantic discussion

from Watch.add to main Watch section

Thanks,

Craig

-- Mr. Craig Gemmill 

Document Name:

obix-v1.1-wd19.pdf

Description

OBIX Specification v1.1, Working Draft 19

* Reworked Section 5.4, Models/Encodings/Bindings

* Added versioning section

* Minor update to Watch language to move semantic discussion

from Watch.add to main Watch section 

Download Latest Revision

Public Download Link

Submitter: Mr. Craig Gemmill

Group: OASIS Open Building Information Exchange (oBIX) TC

Folder: Standards

Date submitted: 2013-11-26 11:43:25

Revision: 1