I know you want to discuss Issue 48.
It would be helpful, and saving of meeting time, if I had a list of issues. I can have a browser open, tabs for each issue, and ready to discuss if the time arises.
Same for any/everyone who wants to submit a list of issues for discussion. It is useful to segment the list into separate lsits for each document to be discussed. This saves fumble time during the meeting, and
lets us be more productive.
"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
Chair, OASIS oBIX TC
Editor, OASIS EMIX, Energy Interoperation
Finance & Administration IT
University of North Carolina
Chapel Hill, NC
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of Markus Jung
Sent: Wednesday, October 02, 2013 10:24 AM
Subject: Re: [obix] OBIX Meeting 10/3/2013
There is now also an updated version of the Encodings document. Addressing several Jira issues.
This could be also an agenda item for one of the next telcos. Some of the resolved issues need a small dicussion.
Since the tomorrow's telco has already a lot of agenda items, I propose to discuss it on October 10th.
Am 01.10.2013 15:28, schrieb Considine, Toby:
As agreed to last week, the first topic for discussion is the WebSockets binding. Several members have converted from Observers to Participants for this conversation. If you plan to speak during this meeting and you are currently enrolled
as an Observer, you still have a couple days to address this process. It is my hope that we can provide the editor with sufficient guidance that we can vote to release the WebSockets binding for Public Review next week.
Thereafter, we will continue to focus on the core spec (OBIX 1.1). Craig has significantly re-arranged the structure of the document and it is worth a complete re-read. There are still numerous formatting issues, some in tormenting Word
to do what it is told, so comments about the tables are not a good use of committee time this week. Please read for sense, and for logical flow.
We still have not discussed the revised XML schema in any depth. As this is the normative description of the energy model, please look closely to this. For XML encodings, the schema *IS* the normative serialization as well. Other
encodings should be a simple transform away from this schema. Please look for breaking changes.
The various editors continue to work on the encodings and bindings specifications, but I am not aware of questions on them for this week’s meeting.
Look to the chat for final information on dial-in 10 minutes before the meeting.
"You can cut all the flowers but you cannot keep spring from coming."
Dipl.-Ing. Markus Jung
Tel. +43 1 58801-18322
Fax +43 1 58801-18391
Institute of Computer Aided Automation
Treitlstr. 1-3/4. Stock/E183-1
Vienna University of Technology