FW: Scraps of Pseudo-XSD

“The single biggest problem in communication is the illusion that it has taken place.”

– George Bernard Shaw.

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: Chet Ensign [mailto:]

Sent: Monday, March 17, 2014 1:41 PM

To: Considine, Toby

Cc: 

Subject: Re: Scraps of Pseudo-XSD

 

Hi Toby, 

 

Patrick and I kicked this around and he suggested as an alternative: 

 

*****

For clarity, this document contains numerous “schema fragments”, that

is, XML descriptions of portions of the OBIX schema in conjunction with

the discussion of each semantic element. Those fragments are

non-normative. The normative version of those "schema fragments" in

their XML schema is (insert schema reference).

*****

 

However, we are also fine with the wording you all have put together. You have done a really good job of clarifying what practitioners are to rely upon. 

 

Best, 

 

/chet

 

On Fri, Mar 7, 2014 at 10:41 AM, Considine, Toby <> wrote:

Chet, TAB

 

During the TAB review of the OBIX specification, comments were made about the examples and the “schema fragments”. Section 1.6, which addresses the former, describes all examples
 as non-normative. I have proposed the final  paragraph be added to section 1.6, below.

 

Does this meet the concern? If not, is there standard boilerplate for this? If there is, I did not find it the most recent templates I have received.

 

Thanks

 

tc

 

1.6 Editing Conventions

For readability, Element names in tables appear as separate words.  In the Schema, they follow the rules as described in Section 1.5.

Terms defined in this specification or used from specific cited references are capitalized; the same term not capitalized has its normal English meaning.

 

All sections explicitly noted as examples are informational and SHALL NOT be considered normative.

 

All UML and figures are illustrative and SHALL NOT be considered normative.

 

For clarity, this document contains numerous “schema fragments”, that is, XML descriptions of portions of the OBIX schema in conjunction with the discussion of each semantic element.
 These fragments are normatively presented in the associated XML schema definitions (XSD).  In accord with OASIS policy, the machine readable XSD is normative. Despite the Technical Committee’s best efforts to keep the schema fragments aligned with the XSD,
 discrepancies may be present. Practitioners SHALL rely upon the XSD in case of any conflict.

 

 

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

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

 

 

 

 

-- 

/chet 

----------------

Chet Ensign

Director of Standards Development and TC Administration 

OASIS: Advancing open standards for the information society

http://www.oasis-open.org

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