I didn’t see
any questions from you, although there seems to be some
from either Ludo or Bill.
I don’t think
any of these require changes to the spec. I will address
what questions I see here, please let me know if I’m
· The obix:int type defined in 18.104.22.168
maps to an xs:long. The schema and the figure both need
to reflect this.
· The root abstraction is “Object”.
This is abbreviated in encoding as “obj”. I’m not sure
how the text on 324-325 is incorrect, because it uses the
term Object consistently. An Object can implement zero or
more Contracts (not just zero or one). Assuming the
request was to make line 344 (and not 324) singular, I
disagree. An Object must be allowed to implement any
number of Contracts. What about an alarmable sensor
point, that must implement obix:Point obix:Alarm
· A contract is NOT just an alias for
anyURI, I don’t think. Maybe only in the XSD, although
I’m not sure I agree with even that restricted statement.
I’m not a schema guru, so I could be wrong, it just seems
like an oversimplification to me.
So, these are
the only questions I’ve seen, and I don’t see any changes
necessary yet to WD36. If you think we need something
new, let me know, or if there is a new XSD we can include
Toby Considine [mailto:email@example.com]
On Behalf Of Toby Considine
Sent: Tuesday, October 21, 2014 1:15 PM
To: Gemmill, Craig
Subject: RE: [obix] OBIX Deadline today
Did you see
my ?s on Schema?
are seldom good technological solutions to behavioral
-- Ed Crowley
anything to do? I have not seen any comments from anyone
that would require any further effort. Let me know if you
need me to provide something else before the vote. I’m in
meetings all day today, tomorrow, and Thursday (although I
plan to try and step out for the TC meeting).
Remember that we need complete packages
for all OBIX specifications today.
A complete package is a Zip archive
1) Editable form
form (PDF w/ Line Numbers)
3) Any Artifacts
(XSD, WSDL as appropriate or needed)
We vote on the entire archive.
We also need to prepare a document
showing differences between this version and the one used
for the last Public Review. Drop me a line if you need
assistance preparing this.
We also need an issue resolution report
(from Jira) for all issues. If you have any Jira issues make
sure that they are up-to-date. If you must prioritize, I’d
rather get the packages today, and Jira updated tomorrow. I
can then prepare resolution reports from Jira.
We hope to vote the complete set out for
public review this week, then turn to the white paper.
"Debugging is twice as hard as writing
the code in the first place. Therefore, if you write the
code as cleverly as possible, you are, by definition, not
smart enough to debug it."
Brian W. Kernighan