OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

energyinterop message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-238) There is notenough clarity in how ws calendar and emix are used within the context ofEI.



    [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23654#action_23654 ] 

Ed Koch  commented on ENERGYINTEROP-238:
----------------------------------------

There were a lot of comments from a lot of different people related to how ws-calendar is used in EI.  If we assume that we aren't all that dense then perhaps the relevant information is more in the editors head than it is on paper.  Just making a broad refernce to ws-calendar and saying that it is used for all scheduling is akin to saying we are writing a standard that uses Language::English.  While it may be correct it isn't very enlightening. I'm not looking for a re-defintion of ws-calendar in the spec, but presumably we are using ws-calendar in some fairly specific ways that should be depicted somewhere.  For example I see nothing in the UML that shows the multi-dimensional nature of the schedules associated with the EventInfo instances.  I agree that we should use ws-calendar for that purpose, but the UML does not depict that aspect of the schedule which in my opinion should show that aspect of our EiEvent schedules.  Again this is not an argument on whether we should be using ws-calendar, but simply further specification on how "EI" is using ws-calendar.

> There is not enough clarity in how ws calendar and emix are used within the context of EI.
> ------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-238
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-238
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: spec
>    Affects Versions: wd16
>         Environment: Ed Koch
>            Reporter: Ed Koch 
>            Assignee: William Cox
>            Priority: Minor
>
> There are two issues with the way we are referencing ws calendar and emix within the EI doc. The first is that we are making wholesale references without any examples of how it is used to satisfy the requirements of EI so it is hard to evaluate wether their use is appropriate.  The second is that presumably emix and ws calendar are standards that have their own scope and could be used for things other than EI.  Therefore it is important to further specify how those standards are constrained and instantiated within EI.  I made a comment related to this earlier related to references to ws calendar within EiEvent,  I have the same concerns with emix.

-- 
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]