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] Updated: (ENERGYINTEROP-584) Program definition in section 5.2.1 is not appropriate for its intended purpose and should be deleted.


     [ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Toby Considine updated ENERGYINTEROP-584:
-----------------------------------------

    Resolution: Misleading Program has morphed into SimpleLevel and Level, no longer suggesting that this conveys a Program.

> Program definition in section 5.2.1 is not appropriate for its intended purpose and should be deleted.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ENERGYINTEROP-584
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-584
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>    Affects Versions: wd29
>            Reporter: Ed Koch 
>            Assignee: Ed Koch 
>             Fix For: wd30
>
>
> Program definition in section 5.2.1 is not appropriate for its intended purpose. It is wholly inadequate and starts to tread into the realm of meta-data for programs which should not be addressed in verion 1.0 of the spec. When we do start adding meta data about programs this information should not be in the event and we should create a seperate program service with accompnaying data strcutures to express the program meta-data. Examples of meta-data we might include about a program include the following:
> - What are the program constraints, i.e. when can I expect to get signals
> - What signals can I expect to receive when I do get an event
> - For each signal what are the attributes of the signal, including type and value constraints where appropriate.
> - What type of feedback (reports) should be generated for this program
> If everyone recalls there use to be a seperate program service and one of the reasons that we deleted it was becasue we did not want to flush all this out in 1.0. In one of our TC meetings in April we decided to put this sort of program meta-data off to 1.1.
> Below I propose an alternate solution that I think will achieve the intended goal of section 5.2.1 in a much more effective fashion and not tread too far down the program meta-data rat hole.

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