WSCALENDAR-409
On 1322, you usually write "start date and time". On 1323 "start-times" is hyphenated, but not elsewhere- WSCALENDAR-407
Line 370 - This sentence conflates WS-Calendar, iCalendar, xCal, AND talks about a WS-Calendar MESSAGE. This is an INFORMATION MODEL. Fix this sentence. - WSCALENDAR-406
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 - WSCALENDAR-405
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" - WSCALENDAR-404
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"?! - WSCALENDAR-403
Line 354-356 - Change "are a critical component of service alignment using WS-Calendar" to "are a critical way to describe service coordination." - WSCALENDAR-401
Line 344 - This discussion is weakened by the lack of either italics or quotation marks around the strings such as "1M" - WSCALENDAR-398
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. - WSCALENDAR-396
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. - WSCALENDAR-391
Line 180 - Capitalization is variable, look at VTODO and vtodo in the first two lines. - WSCALENDAR-390
Line 147 - Replace "An ancillary..." with "An additional..." or "Another...". (mild preference) - WSCALENDAR-385
Line 49 - delete "(WS-Calendar)" - WSCALENDAR-384
Lines 43-48: the intent matters less that what is produced in the document in our hands. - WSCALENDAR-382
DP-WS has a hyphen on line 24 and not on line 64 - WSCALENDAR-378
Line 13 - "agent" has many meanings. Perhaps "actor" would be a better choice? Agency is not what's suggested here. - WSCALENDAR-377
Sentence starting line 4: "Agreement on when something should or did occur is fundamental to negotiating service use." - WSCALENDAR-376
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]." - WSCALENDAR-375
Footnote 3 page 9 - Is OPC UA a trademark? If not, why is it footnoted? - WSCALENDAR-374
Footnote 2 and 4 page 9 Footnote is repeated. Note that only the first use a a registered trademark could or should be footnoted. - WSCALENDAR-373
Section 1 line 2 and the rest of the specification: Change "Semantic Model" to "information model" throughout the document - WSCALENDAR-372
Line 1646 - "Xs:bool" differs how from "xs:bool" and how do they relate to the W3 XML Schema type "boolean"? Fix - WSCALENDAR-370
Line 1646 - Should "shall" be "SHALL" in the definition? - WSCALENDAR-367
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. - WSCALENDAR-366
Line 869 - Granularity is also on line 718; needs to be related and explain why different (if it is) - WSCALENDAR-365
Line 887 - why is "availability" different from "vavailability"? - WSCALENDAR-359
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] - WSCALENDAR-358
Line 858 - "Designated Interval" text should reference line 196 - WSCALENDAR-355
Line 718 - Capitalization of first column is not consistent with other tables - WSCALENDAR-354
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. - WSCALENDAR-352
Line 462 - Reference table 1-3 where "Sequence" is defined. - WSCALENDAR-351
Line 395 - The capitalization seems almost random across the tables - WSCALENDAR-349
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 - WSCALENDAR-345
Table 3-3 ? there IS NO TABLE 3-3.
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
0.3
0