1. Sub-task WSCALENDAR-408
    Line 1321 - Why is "Service Advertisements" in the heading? This is more than just "service adv" - should this be "describing" or "managing" "start times"?
  2. Sub-task WSCALENDAR-402
    Line 354-356 - We have Intervals, now we have Time Segments? I don't find a definition, and it seems very similar.
  3. Sub-task WSCALENDAR-395
    Line 223 - The section title again may lead to confusion between whether this is an information model or a service definition. it is the former; and time semantics are not critical to JUST WS-Calendar. reconsider the focus and message of this paragraph
  4. Sub-task WSCALENDAR-394
    Line 205 - Compare this first paragraph with e.g. line 43 which talks about what the intent was; this paragraph is in better voice describing how the work was produced.
  5. Sub-task WSCALENDAR-393
    Line 180 - For Gluon add in definition a footnote "Sometimes referred to as a Calendar Gluon". Or correct use of "Calendar Gluon" in the rest of the document to "Gluon" [preferred].
  6. Sub-task WSCALENDAR-371
    Line 1646 - The discussion of "components" at "the realm border" and "overwrite without notice" seems out of place in an information model.
  7. Sub-task WSCALENDAR-369
    Line 1646 - timeStampRealm - do you really mean "A set of points ..."? A set of timestamps? A set of locations?
  8. Sub-task WSCALENDAR-368
    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.
  9. Sub-task WSCALENDAR-344
    Table 3-2 is Temporal Relationship/Short Form/ Definitioin/Example - is this because these are DEFINED in WS-Calendar rather than USED?
  10. Sub-task WSCALENDAR-343
    Table 3-1 headings are Elements/Use/Use in WS-Calendar. Isn't this the WS-Calendar draft standard?
  11. Sub-task WSCALENDAR-324
    Line 1873-1874 - the use of the word "owner" may be interpreted to apply to certain data, then a term other than "owner" should be used to avoid the legal implications associated with using the term "owner"
  12. Sub-task WSCALENDAR-308
    PR02 What are you defining? XCAL? WS-Calendar? Some combination?
  13. Sub-task WSCALENDAR-282
    Line 870 - the defintion of "Bound" in Table 1-6 does not include Duration, as in "Bound Duration" employed in the sentence.
  14. Sub-task WSCALENDAR-276
    Line 453-465 - it appears that this language would be better served if the heading 3.1.4 appeared before the text that starts on line 453.
  15. Sub-task WSCALENDAR-274
    Line 452 - "The two expressions of a Temporal Relationship above are equivalent" appears after THREE examples of temporal relationships. To which two is this statement referring?
  16. Sub-task WSCALENDAR-273
    Line 395 - "Example" of "finishToFinish" does not appear to align with the "Definition".
  17. Sub-task WSCALENDAR-272
    Line 392-394 - it is unclear which elements are used from RFC 5988 from the list of elements in Section 6.2.2 of that RFC - explicitly clarify elements
  18. Sub-task WSCALENDAR-268
    Line 271 - "Practitioners should consult..." refers to practitioners of what exactly? WS-Calendar? "Which Time? UTS vs. Local Time"? - clarify "practitioners"
  19. Sub-task WSCALENDAR-263
    Line 2657-2661 - this text appears to align with item #4 in the bulleted list in 5.2 (line 2624) yet has no heading - add heading for this set of language: 5.2.4 Covarying Attributes
  20. Sub-task WSCALENDAR-259
    Line 1022 - "Partitions are Sequences composed of consecutive Intervals" appears to be in conflict with line 180 "A Partition is a set of consecutive Intervals."
  21. Sub-task WSCALENDAR-258
    Line 1020 - does "availability" in the rules for Schedules and Availability mean "Availability" as defined in the document?
  22. Sub-task WSCALENDAR-253
    Line 369-370 - The statement about "unanchored interval" both repeats the statement about "unscheduled interval" in 362-363 and appears to disagree with the definitions in 196 Table 1-6.
Refresh results