1. Improvement WSCALENDAR-454
    Improve orthogonality of Binding / Inheritance etc.
  2. Improvement WSCALENDAR-453
    Collector for rules involving dtStart, dtEnd and Duration
  3. Bug WSCALENDAR-451
    Appendix
  4. Bug WSCALENDAR-450
    Section 4 - RESTful services
  5. Sub-task WSCALENDAR-449
    Section 5 - Conformance and Rules
  6. Bug WSCALENDAR-445
    All - The use of web services has been assumed or mandated where not all other standards that use ws_calendar have the same assumption or mandate.
  7. Bug WSCALENDAR-442
    Section 3.3.1.1 - Gluons are another example of a multi-purpose, you don't need it unless it's present class in this standard. It lacks a specific purpose therefore it was very hard to name.
  8. Improvement WSCALENDAR-439
    Section 3.1.4.1 - Not creating a new type for an "anchored sequence" makes validation very difficult.
  9. Bug WSCALENDAR-438
    Section 3.1.4.1 - Is there some way to define a sequence and then re-use it in several "anchored sequences"
  10. Bug WSCALENDAR-437
    Section 3.1.2 - "An Unscheduled Interval " - Are these terms consistent/overlapping with table 1.6
  11. Bug WSCALENDAR-436
    All - Where is the information model (class model)? The widespread use of inheritance would have been better understood with an inheritance model.
  12. Bug WSCALENDAR-433
    Section 2.2 - ", the service scheduled to shed load " - How does this example change this spec?
  13. Sub-task WSCALENDAR-431
    All - The standard provides every possible method to define intervals and schedules while this is clever it does not increase the chance of interoperability.
  14. Bug WSCALENDAR-430
    Table 1.6 - What values? (Calendar date?)
  15. Improvement WSCALENDAR-424
    All - the use of generic data types make it impossible to determine the actual intent of the message and limits validation. An error would change the intent of the message with no way of knowing that an error had occurred
  16. Sub-task WSCALENDAR-422
    Add reference to vavailability schema to table 1-2
  17. Bug WSCALENDAR-414
    Line 2676 - Actionable services require Bound Intervals as part of a Bound Sequence. Services may Intervalsarenot bound for informational or negotiation purposes.Some of these are modeled an constraints in the UML models that have been produced separately
  18. Bug WSCALENDAR-412
    Line 311 - Parameters are not discussed
  19. Improvement WSCALENDAR-411
    Support for randomized intervals is desirable in many applications. Suggest adding one or more randomization parameter types. Should be applicable to start, end, or duration.
  20. 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"?
  21. 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.
  22. 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.
  23. Sub-task WSCALENDAR-389
    Line 124 - I believe that this should be [NAESB_PAP04] and reference both the first and second release.
  24. Sub-task WSCALENDAR-383
    Line 34 - there is no reference for [EITC] and [EMIX]; these should be non-normative references. Likewise EDXL and oBIX on lines 35-36
  25. Sub-task WSCALENDAR-379
    Cover and starting on line 59: The RFCs listed seem to be out of sync (in the normative references. Verify that current dates are used; Vavailability has been recently updated.
  26. Bug WSCALENDAR-364
    Line 887 - Uid, Summary, dtStart, dtEnd, duration, and Granularity
  27. Bug WSCALENDAR-360
    Line 881 - "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).
  28. Bug WSCALENDAR-353
    Line 464 - The relationship may not be determinable if the reltype is inherited along with duration and dtstart until the sequence is Bound.
  29. Bug WSCALENDAR-347
    Section 3 - Table headings change and confuse
  30. Improvement WSCALENDAR-342
    Is there a standard vlue for durations of Month and Year?
  31. Improvement WSCALENDAR-341
    Collector for Reference Checks
  32. Improvement WSCALENDAR-339
    Collector for Editorial - muddled defintions or writing
  33. Task WSCALENDAR-337
    Collector for Schema Profiling and Simplification
  34. Improvement WSCALENDAR-335
    Collector for Schema Issues
  35. Sub-task WSCALENDAR-317
    Line 837 - delete "[reference]" and insert the appropriate reference
  36. Sub-task WSCALENDAR-308
    PR02 What are you defining? XCAL? WS-Calendar? Some combination?
  37. Bug WSCALENDAR-307
    Technical issues in Section 3 tables
  38. Bug WSCALENDAR-306
    Text and Reference Issues PR02
  39. Sub-task WSCALENDAR-305
    Simpler and more constrained information model in addition to the PR02 information model
  40. Improvement WSCALENDAR-304
    Collector for Mechanically Editorial Issues
  41. Sub-task WSCALENDAR-280
    Line 718 - Change first column heading to "Parameter"
  42. Sub-task WSCALENDAR-279
    Line 718 - Change Table heading to "Tolerance Parameters"
  43. Sub-task WSCALENDAR-278
    Line 706 - heading is unclear and more explicit reference to Tolerance would be appreciated
  44. 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
  45. Bug WSCALENDAR-260
    Line 718, 1646 - are the items in the tables "parameters", "aspects" or "elements" - make consistent throughout document
  46. Sub-task WSCALENDAR-258
    Line 1020 - does "availability" in the rules for Schedules and Availability mean "Availability" as defined in the document?
  47. Bug WSCALENDAR-238
    Line 1774 - [web linking] is undefined
  48. Sub-task WSCALENDAR-229
    Remove any unused types from the schema, probably replace with some form of annotation.
  49. Sub-task WSCALENDAR-227
    define the "components" and "properties" elements at the top level
  50. Sub-task WSCALENDAR-225
    The availability extension was not imported.
  51. Sub-task WSCALENDAR-224
    Ws-Calendar looks to be a terrific advance for the smart grid and providing ways for users to use only what they need without having to understand all of Ws-Calendar.
  52. Improvement WSCALENDAR-223
    All uses of granularity are not clear
  53. Sub-task WSCALENDAR-222
    Recurrence Rules seem recursive, Unable to build VAvailability
  54. Bug WSCALENDAR-219
    Table 1.4 Gluon - relationships inverted
  55. Bug WSCALENDAR-218
    Line 189 - Table 1.4 Temporal Relationship needs change
  56. Improvement WSCALENDAR-208
    Create better explanation of different parts of WS-Calendar: Semantic, API (REST), and Message (SOAP) and which parts to use when
  57. Sub-task WSCALENDAR-207
    Duplicate Issue
  58. Improvement WSCALENDAR-199
    All - Should the xml file scripts be limited to a certain number of characters such that the file could be sent via SMS text messaging or possibly via the radio data service (RDS) broadcast service.
  59. Improvement WSCALENDAR-198
    All - Given the different context with which a timing mechanism can be used, for which contexts does this proposed standard apply?  E.g. dispatch, settlements, operations characteristics, scheduling tags, bilateral schedules... 
  60. Improvement WSCALENDAR-193
    Line 692 - While physics is an interesting subject, this is not a PBS show and talking about gluons and quarks sounds neat, but is a distraction. If the term gluon needs to stay fine, but there might be better terms.
  61. Bug WSCALENDAR-179
    Line 135 - The framework as it stands define the services execution context. The RTO can't endorse unless and until the policy context is defined. When and would the policy context be defined ?
  62. Improvement WSCALENDAR-178
    Line 41 - "Normative" reference intent. Is interpreted to mean Standards forming ? If so what are the business processes affected and performance benchmarks for compliance ?
  63. Improvement WSCALENDAR-170
    Line 366 - Agree with Sean's comment - how is this structured? Or is it explicitly unnecessary?
  64. Improvement WSCALENDAR-161
    Line 712 - This is a class definition and declaration in one?
  65. Improvement WSCALENDAR-149
    Section 8.18 - If 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".
  66. Improvement WSCALENDAR-146
    Line 1836 - Why does the example return an icalendar tag rather then a wscalendar tag?
  67. Bug WSCALENDAR-143
    Inheritance model - Inheritance model appears similar to CSS in that once defined, a term persists until overriden by a contained element. If this is so, a reference to this might make sense.
  68. Bug WSCALENDAR-127
    The use of iCalendar to schedule device services across a large domain of buildings (or equipment within a building) could have the unintended effect of load synchronization.
Refresh results