[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ENERGYINTEROP-697) Conformance with WS-Calendar
[ https://issues.oasis-open.org/browse/ENERGYINTEROP-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Cox updated ENERGYINTEROP-697: -------------------------------------- Fix Version/s: ctsWD17 Resolution: Corrected reference to show CAL-MIN not [WS-Calendar] A future draft will add an Informative Appendix to describe conformance with the TEMIX profile of Energy Interoperation (using the methods of IEC 62746-10-3) Assignee: William Cox (was: Toby Considine) > Conformance with WS-Calendar > ---------------------------- > > Key: ENERGYINTEROP-697 > URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-697 > Project: OASIS Energy Interoperation TC > Issue Type: Bug > Components: cts > Affects Versions: CTSPR01 > Environment: H Walter JohnsonÂhttps://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00007.html > Reporter: Toby Considine > Assignee: William Cox > Priority: Minor > Labels: ARCH-CONF > Fix For: ctsWD17 > > > When discussing Conformance (Section 14), line 780 says Portions of CTS conform to and use updated and simplified versions of the specifications. I guess it's possible for a spec's conformance rules to allow the CTS spec to both conform to it and to extend it, but it does sound somewhat paradoxical. Besides, the WS-Calendar spec says [lines 1553-1554] that "Specifications that...claim conformance with WS-Calendar SHALL define the business meaning of zero duration Intervals and I don't find that in the CTS spec. -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]