[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Created: (WSCALENDAR-307) Technical issues inSection 3 tables
Technical issues in Section 3 tables
------------------------------------
Key: WSCALENDAR-307
URL: http://tools.oasis-open.org/issues/browse/WSCALENDAR-307
Project: OASIS Web Services Calendar (WS-Calendar) TC
Issue Type: Bug
Affects Versions: pr02
Environment: William Cox
Reporter: William Cox
Assignee: Toby Considine
This item lists technical issues in the tables for Section 3.
Section 3
Table headings change and confuse. Table 3-1 headings are Elements/Use/Use in WS-Calendar. Isn't this the WS-Calendar draft standard?
Table 3-2 is Temporal Relationship/Short Form/ Definitioin/Example - is this because these are DEFINED in WS-Calendar rather than USED?
Table 3-3 ? there IS NO TABLE 3-3.
Table 3-4 is Attachment Element/Use/Discussion, and the discussion for Text seems out of place.
This is confusing to the reader and should be made more clear, either by introductory text that says why the different formats are used, or using the same format. I'd suggest "definition" means "defined in ws-calendar" and "use" means used but not defined in ws-calendar.
Line 368
Both DtStart and Duration are "optional". What precisely does that mean? That neither need to be present? we find later that these values can be inherited from a gluon, but at this point "optional" seems to mean "no value is required"
Why is "attach" not capitalized? that doesn't fit the style of some tables (but see Table 3-2)
"attach" mixes "attach" and "Attach". Are they different? Is case important in these tables and the schemas? XML is case sensitive, and this confuses.
Elsewhere it's recommended that intervals have DtStart and Duration (either of which can be filled in through e.g. inheritance), but we see later an odd blend (line 858 adds DtEnd to the mix). This needs to be clear and consistent across the document.
Line 395
The capitalization seems almost random across the tables; tables 3-1 and 3-2 are not consistent with each other, table 3-1 is not consistent with itself. In Table 3-2 only "Gap" is capitalized. If there's a capitalization rule for the tables it should be explained and followed consistently.
Line 462
Reference table 1-3 where "Sequence" is defined.
Line 464
The relationship may not be determinable if the reltype is inherited along with duration and dtstart until the sequence is Bound.
Line 718
Reference to "service" seems out of place; consider "operation" as an alternative. On line 712, "service coordination between systems' really should read "action coordination between/across systems" I think.
Capitalization of first column is not consistent with other tables.
Line 858
dtEnd is not listed and optional, as are dtStart and duration (DtStart and Duration?) THe "duration" line item is actually an element called "duration" of type "Duration". To describe its "use" as "Duration" is incorrect; consider "express Duration"
dtEnd says "SCHEDULED completion time..." is this implied or computed or expressed? dtStart simply says "Start time"
"Designated Interval" text should reference line 196
WsCalendar Attach the use is "WSCalendar:Attachment" this is very unclear. "The Attach element contains..." and change "incorporating specifications" to "conforming specifications" [ref to section 5.4]
Line 881
Table 3-7.
"use" of "Summary" is not "text" - that's its type. The "Discussion" belongs in use. or change the column heading "Use" to "Type" (but stay consistent with other tables).
The "optionality" of dtEnd and duration is not clearly defined. You need one or the other per the text on line 882 (unless having an undefined end is fine - not clear from the text). Unbounded recurrence is fine, if that's what's intended by no dtEnd/duration.
Line 877
Vavailability is a 3 year old proposal; there's an update, but are you defining what it is in this document? Fine to do so, but is this in the spirit of Vavailability or mappable to or identical or decoupled? Not clear; make it more clear. Generally decoupling is safer, but if vavailability is being defined in conjunction with this work product, then there are fewer issues.
Line 887
The relationship of tables 3-7 and 3-8 is not clear. They are largely the same, and seem in part a quotation of another specification. I was told verbally that RRule is not used. Is Granularity? is it the same as the granularity in the definition at line 718? Different? Why? If you're extending a standard definition for vavailability then you could indicate the base elements with an asterisk or other convention.
The near identity of Uid, Summary, dtStart, dtEnd, duration, and Granularity makes one wonder why Uid and RRule are only in table 3-8, and why dtStamp is only in table 3-7 along iwth Availability. If there's a recurrence pattern or recursive inclusion that should be made very clear.
And why is "availability" different from "vavailability"?
Line 869
Granularity is also on line 718; needs to be related and explain why different (if it is).
Line 898
Typographically distinguish e.g. 15M, 30M, etc, as suggested elsewhere. If these are strings, put in italic or bold, but be consistent through the document.
Line 1020
Why is "Schedules" plural? You use "schedule" in other places. Is this the name of the attribute? Rather it's the description of a collection of attributes/elements.
Line 1646
timeStampRealm - do you really mean "A set of points ..."? A set of timestamps? A set of locations?
Should "shall" be "SHALL" in the definition? Now the column headers are Time Stamp Element/Defintion/Note. The discussion of "components" at "the realm border" and "overwrite without notice" seems out of place in an information model. Delete the rules for setting or clarify that this is an information model, and "it is expected that use will follow these requirements"
"Xs:bool" differs how from "xs:bool" and how do they relate to the W3 XML Schema type "boolean"? Fix.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]