| Toby,
I cannot tell you if you need to put any breaks on as Chet or Robin would be better able to do so, but the question about copyright and attributions for the iCalendar schema led to the realization that the harmonization agreement needed to be updated and ratified and agreement reached on proper wording for the header comments and such. That's being worked now as you will have noticed via the e-mail from Jamie earlier today.
Dave
On Jun 13, 2011, at 2:54 PM, Toby Considine wrote: Chet: Last week, in a quorate meeting, on a roll call vote, the TC directed the Chair to deal with this, if possible, working with TC-Admin. (Can we have minutes posted soon?) Mikes proposal is a trivial difference in implementation. Is that good enough? BTW, this is also an open call for any TC members to put a hand up and put the brakes on… I am suggesting this acceleration because I know you will be out on Friday and for the next week. tc
"He who fights with monsters should look to it that he himself does not become a monster, and if you stare long into an abyss, the abyss also stares into you." - Fredrich Nietzche
Toby Considine
TC9, Inc TC Chair: oBIX & WS-Calendar TC Editor: EMIX, EnergyInterop U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee
| | |
Toby, Mike - this sounds like you have a few changes that you need to make. Toby, can you do the following for me? - Coordinate on any changes you need to make. Package a new, complete set of documents for the CSD into a new zip. - Have the TC pass a motion approving the new zip as the approved set of files for WS-Calendar v1.0. I can help set up a ballot in Kavi if that will assist. - Once the TC has approved, add a comment and a link to the approved zip file to the JIRA ticket at http://tools.oasis-open.org/issues/browse/TCADMIN-516. You can simply indicate that the TC has approved an updated package to replace the originally listed submitted zip file - pls put the link to the approval as well as the zip. Since we have not yet started work on the CSD we'll accept this change to the ticket without changing its priority. If for some reason you can't update that ticket yourself let me know and we'll work something else out. We can do the initial set up of the template - the URI's and such - while you get that sorted out, so this should not affect your turnaround time. Let me know if you have any questions... On Mon, Jun 13, 2011 at 4:09 PM, Mike Douglass < douglm@rpi.edu> wrote: I missed this message: - been fixing up some crises of my own here
Where is it used as a parameter? I've searched the spec and the only place granularity turns up is as an element of the tolerance property.
We did discuss adding it as a PROPERTY.
The word "parameter" turns up at line 1053 - it should be "property"
Also the work component is used incorrectly
Replace
WS-Calendar adds a single optional parameter to the [Vavailability] component. When a Granularity component is applied, it further defines the acceptable service invocation.
WS-Calendar adds a single optional property to the [Vavailability] component. When a Granularity proeprty is applied, it further defines the acceptable service invocation.
Section 3.3.1.3 is fine if we respecify the granularity as a property.
Also at line 1409 it's mentioned again but isn't in the example following.
As I recollect the discussion around this we had on Friday resulted in the following:
1. The Tolerance property has a "granularity" value element. This should be renamed to "precision" as that is what it's trying to express and it removes confusion with the following:
2. We add a granularity PROPERTY which can be applied to vavailability or availability to define the size of the 'chunks' of time
The tolerance property can be applied to the calendar component to act as a default for the entire set of components or added as a property to a single component to override any default.
I think the only change to the examples would be line 1100 and to add a granularity property somewhere around 1416-1463
I can send an updated schema with the changes
On 06/11/2011 05:40 PM, Toby Considine wrote:
In the schemas for ws-calendar, the granularity parameter was lost during some final edits. <xs:element name="granularity" type="xcal:DurationParameterType" substitutionGroup="xcal:baseParameter"/> This should have appeared after line 21 of the schema file iCalendar-wscal-extensions.xsd The parameter appears in the Specification, and is used for several documented purposes. It is also critical to several parts of EMIX and Energy Interoperation. Its absence is due to an error in my quality checking of same late-arriving changes that modified the declarative patterns in some other schema types. It was discussed in Friday’s meeting, with the acknowledgement that this would drive the production of a PR04, with associated delays of other standards. No one in the quorate call was vwn aware that it Had dropped out until I brought it up. This is clearly a procedural violation, but if it can be fixed before the schemas go out, it would enable to the samples, specifications, and schemas to match. CC’ing the TC in the interests of transparency and to allow any of them to protest, if anything path is suggested to fixing this prior to publication. tc
“The single biggest problem in communication is the illusion that it has taken place.”
– George Bernard Shaw.
Toby Considine
TC9, Inc TC Chair: oBIX & WS-Calendar TC Editor: EMIX, EnergyInterop U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee | | |
-- Mike Douglass douglm@rpi.edu Senior Systems Programmer Communication & Collaboration Technologies 518 276 6780(voice) 2809 (fax) Rensselaer Polytechnic Institute 110 8th Street, Troy, NY 12180
--
/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-378-3472
Mobile: +1 201-341-1393
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
|