Michel,
I’ll leave it to Bill to properly
characterize what we are voting on, but we are not yet voting on approving any
schemas. It is far too premature for that. Until we get input from UCA and
the pricing/scheduling task force we don’t even yet know what information needs
to be added to the current specification much less design and approve schemas
for it.
We can and should discuss the issues you
raise if for no other reason that to better understand the current OpenADR
specification, but I don’t think our first vote should be contingent on those
discussions.
-ed koch
From: Wilson, David C
(St. Paul)
[mailto:DavidCWilson@trane.com]
Sent: Wednesday, August 05, 2009
4:52 AM
To: michel@universal-devices.com;
energyinterop@lists.oasis-open.org
Subject: Re: [energyinterop] XSD
Files for Committee Draft 01
To Michel's point, I think there is interest in
changing the schema in a few ways. Bill advocates making those changes "in
public" by revising after the first committee draft is published. (If I
understood him correctly.)
That is really question number one: does this first draft include any
significant changes to OpenADR?
On the enumerations, I advocate an interger state value that is defined in the
specification. This is simpler for an embedded controller to handle. We should
also consider backward compatibility.
Regards,
Dave
Dave
Sent from my mobile device
----- Original Message -----
From: Michel Kohanim <michel@universal-devices.com>
To: energyinterop@lists.oasis-open.org
<energyinterop@lists.oasis-open.org>
Sent: Wed Aug 05 01:21:32 2009
Subject: RE: [energyinterop] XSD Files for Committee Draft 01
Hi David,
I am a little ill at ease with the current XSD. I do think that we need at
least two sessions to go through the objects and decide what’s the best way to
represent them.
My major problem is the mixture of semantics and syntax. i.e. a Type is defined
in XSD and all XML instances of that Type are, well, its instances. As such, I
am a little confused as to why we would have EventInfoInstance (which is a
type) to define instances of the EventInfoType.
Other examples of this problem are “enumerations” which, in and of themselves,
should be “types” but are used as text.
Would it be possible to have two sessions to go through all these objects
before approving this schema?
With kind regards,
********************************
Michel Kohanim, C.E.O
Universal Devices, Inc.
(p) 818.631.0333
(f) 818.708.0755
http://www.universal-devices.com
********************************
From: Wilson, David C (St. Paul)
[mailto:DavidCWilson@trane.com]
Sent: Tuesday, August 04, 2009 8:59 AM
To: energyinterop@lists.oasis-open.org
Subject: [energyinterop] XSD Files for Committee Draft 01
Please be prepared to vote to include the schema files as part of Committee
Draft 01.
The following changes have been made to the schema work contributed from
OpenADR:
· The OASIS copyright notice has been added
(1).
· The namespace root has been changed from
(2) to (3).
· The XSD URI’s have been changed from (4)
to (5).
· An RDDL namespace file draft has been
added.
(1) <!-- Copyright OASIS Open 2009 -->
(2) http://www.openadr.org
(3) http://docs.oasis-open.org/ns/energyinterop/energyinterop-20090701
(4) http://openadr.lbl.gov/src/1/*
(5) http://docs.oasis-open.org/enrgyinterop/xsd/1.0/wd02/*
A current zip file is available at:
http://www.oasis-open.org/apps/org/workgroup/energyinterop/document.php?document_id=33637
<http://www.oasis-open.org/apps/org/workgroup/energyinterop/document.php?document_id=33637>
Regards,
Dave
David Wilson
Enterprise
Solutions Portfolio Manager
Trane Commercial Systems
Ingersoll Rand
Office: +1.651.407.4168
Mobile:
+1.612.741.2759
Email: davidcwilson@trane.com <mailto:JSmith@trane.com>
www.trane.com <http://www.trane.com/>
================================================
Mr. David Wilson added the following comment to the
energyinterop-1.0-xsd-wd02.zip document in the OASIS Energy Interoperation TC
Group.
This revision changed the zip file name to match naming conventions. A
README file was added. The RDDL file was added with a modification to the URI
for the XSD files. The XSD URI was within the namespace URI which is inconsistent
with OASIS guidelines.
View Document Details and Comments:
http://www.oasis-open.org/apps/org/workgroup/energyinterop/document.php?document_id=33637
<http://www.oasis-open.org/apps/org/workgroup/energyinterop/document.php?document_id=33637>
Download Document:
http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/33637/energyinterop-1.0-xsd-wd02.zip
<http://www.oasis-open.org/apps/org/workgroup/energyinterop/download.php/33637/energyinterop-1.0-xsd-wd02.zip>
PLEASE NOTE: If the above links do not work for you, your email application
may be breaking the link into two pieces. You may be able to copy and
paste the entire link address into the address field of your web browser.
- Administration
The information contained in this message is privileged and intended only for the
recipients named. If the reader is not a representative of the intended
recipient, any review, dissemination or copying of this message or the
information it contains is prohibited. If you have received this message in
error, please immediately notify the sender, and delete the original message
and attachments.
The information contained in this message is privileged and intended
only for the recipients named. If the reader is not a representative of the
intended recipient, any review, dissemination or copying of this message or the
information it contains is prohibited. If you have received this message in
error, please immediately notify the sender, and delete the original message
and attachments.