[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (EMIX-250) All - EMIX is buildinginteractions with WSCalendar. Issues with WSCalendar have not beencompletely addressed, thus further issues could present themselves withEMIX when the WSCalendar is completed. Further complications may occurwith Energy Interop.
[ http://tools.oasis-open.org/issues/browse/EMIX-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Cox updated EMIX-250:
-----------------------------
Resolution:
The work of the three OASIS Technical Committees (WS-Calendar, EMIX, and Energy Interoperation) has been carefully coordinated to give opportunity to use and discover issues with each other, as shown in (e.g.) the NIST PAP09 dependency graphs. We view the opportunity to use and improve WS-Calendar due to its use in EMIX and Energy Interoperation as an opportunity to ensure that the specifications are complete and useful. The ordering of public reviews and Committee Specification Drafts has been and is planned to address the issues you raise.
I have posted a comment to Energy Interoperation to ensure that the use of and terminology from WS-Calendar is consistent across the two standards.
Actions in EMIX: Rewrite and review the ws-calendar narrative for clarity and precision, including a discussion of inheritance earlier in document.
Use WS-Calendar Gluon in first reference in each section.
Add conformance section on inheritance to last section.
Terminology needs to be consistent; e.g., a Gluon acts as a handle to a Sequence
Capitalize Interval, Gluon, Sequence throughout as defined terms.
was:
The work of the three OASIS Technical Committees (WS-Calendar, EMIX, and Energy Interoperation) has been carefully coordinated to give opportunity to use and discover issues with each other, as shown in (e.g.) the NIST PAP09 dependency graphs. We view the opportunity to use and improve WS-Calendar due to its use in EMIX and Energy Interoperation as an opportunity to ensure that the specifications are complete and useful. The ordering of public reviews and Committee Specification Drafts has been and is planned to address the issues you raise.
have posted a comment to Energy Interoperation to ensure that the use of and terminology from WS-Calendar is consistent across the two standards.
Rewrite and review the ws-calendar narrative for clarity and precision, including Stop sentence after "inherited" and add discussion of inheritance earlier in document.
Use WS-Calendar Gluon in first reference in each section.
Add conformance section on inheritance to last section.
Terminology needs to be consistent; e.g., a Gluon acts as a handle to a Sequence
Capitalize Interval, Gluon, Sequence throughout as defined terms.
> All - EMIX is building interactions with WSCalendar. Issues with WSCalendar have not been completely addressed, thus further issues could present themselves with EMIX when the WSCalendar is completed. Further complications may occur with Energy Interop.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMIX-250
> URL: http://tools.oasis-open.org/issues/browse/EMIX-250
> Project: OASIS Energy Market Information Exchange (eMIX) TC
> Issue Type: Sub-task
> Components: spec
> Affects Versions: csprd01 Public Review Draft
> Environment: IRC
> Reporter: Toby Considine
> Assignee: Toby Considine
> Fix For: wd17
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]