1.
|
Table 3-3 ? there IS NO TABLE 3-3. |
|
Closed |
Toby Considine
|
2.
|
Line 368 - 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 |
|
Closed |
Toby Considine
|
3.
|
Line 395 - The capitalization seems almost random across the tables |
|
Closed |
Toby Considine
|
4.
|
Line 462 - Reference table 1-3 where "Sequence" is defined. |
|
Closed |
Toby Considine
|
5.
|
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. |
|
Closed |
Toby Considine
|
6.
|
Line 718 - Capitalization of first column is not consistent with other tables |
|
Closed |
Toby Considine
|
7.
|
Line 858 - "Designated Interval" text should reference line 196 |
|
Closed |
Toby Considine
|
8.
|
Line 858 - 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] |
|
Closed |
Toby Considine
|
9.
|
Line 887 - why is "availability" different from "vavailability"? |
|
Closed |
Toby Considine
|
10.
|
Line 869 - Granularity is also on line 718; needs to be related and explain why different (if it is) |
|
Closed |
Toby Considine
|
11.
|
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. |
|
Closed |
Toby Considine
|
12.
|
Line 1646 - Should "shall" be "SHALL" in the definition? |
|
Closed |
Toby Considine
|
13.
|
Line 1646 - "Xs:bool" differs how from "xs:bool" and how do they relate to the W3 XML Schema type "boolean"? Fix |
|
Closed |
Toby Considine
|
14.
|
Section 1 line 2 and the rest of the specification: Change "Semantic Model" to "information model" throughout the document |
|
Closed |
Toby Considine
|
15.
|
Footnote 2 and 4 page 9 Footnote is repeated. Note that only the first use a a registered trademark could or should be footnoted. |
|
Closed |
Toby Considine
|
16.
|
Footnote 3 page 9 - Is OPC UA a trademark? If not, why is it footnoted? |
|
Closed |
Toby Considine
|
17.
|
Lines 1-2 - The emphasis on Web services seems strange; consider "The information model of WS-Calendar is intended to be used to define information payloads for Web services and Service-style interactions [SOA-RM]." |
|
Closed |
Toby Considine
|
18.
|
Sentence starting line 4: "Agreement on when something should or did occur is fundamental to negotiating service use." |
|
Closed |
Toby Considine
|
19.
|
Line 13 - "agent" has many meanings. Perhaps "actor" would be a better choice? Agency is not what's suggested here. |
|
Closed |
Toby Considine
|
20.
|
DP-WS has a hyphen on line 24 and not on line 64 |
|
Closed |
Toby Considine
|
21.
|
Lines 43-48: the intent matters less that what is produced in the document in our hands. |
|
Closed |
Toby Considine
|
22.
|
Line 49 - delete "(WS-Calendar)" |
|
Closed |
Toby Considine
|
23.
|
Line 147 - Replace "An ancillary..." with "An additional..." or "Another...". (mild preference) |
|
Closed |
Toby Considine
|
24.
|
Line 180 - Capitalization is variable, look at VTODO and vtodo in the first two lines. |
|
Closed |
Toby Considine
|
25.
|
line 234 - Footnote 6 should have an informative reference [SOA-RM] rather than the "...found in the normative references..." wording. Add [SOA-RM] reference on line 227. |
|
Closed |
Toby Considine
|
26.
|
Line 303 - "Duration" was defined on line 180, and should be capitalized. "schedule" is not defined and should be (and might be as "Schedules" on line 1020). "time" is not defined and probably shouldn't be. |
|
Closed |
Toby Considine
|
27.
|
Line 344 - This discussion is weakened by the lack of either italics or quotation marks around the strings such as "1M" |
|
Closed |
Toby Considine
|
28.
|
Line 354-356 - The final sentence is incomprehensible as written. And it uses "time segment" which was capitalized in the first sentence. And how are "terms about time" contained "within a particular time segment"?! |
|
Closed |
Toby Considine
|
29.
|
Line 354-356 - Change "are a critical component of service alignment using WS-Calendar" to "are a critical way to describe service coordination." |
|
Closed |
Toby Considine
|
30.
|
Line 362 - An Interval is NOT a "unit of service delivery." It's a span of time. The description of "bound to time" should reference "Bound" in table 1-6, and should reference those Semantics Decribing Intervals" |
|
Closed |
Toby Considine
|
31.
|
Line 369 - "Linked to a specific date and time" should be "Bound to a specific [date and] time" The word "tied" could be used, but you've already defined Bound |
|
Closed |
Toby Considine
|
32.
|
Line 370 - This sentence conflates WS-Calendar, iCalendar, xCal, AND talks about a WS-Calendar MESSAGE. This is an INFORMATION MODEL. Fix this sentence. |
|
Closed |
Toby Considine
|
33.
|
On 1322, you usually write "start date and time". On 1323 "start-times" is hyphenated, but not elsewhere |
|
Closed |
Toby Considine
|
Minor 