[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ENERGYINTEROP-630) 5.2.2 Application Specific Extensions appear to violate the statement on 475 on no direct interaction across the ESI.
[ http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28427#action_28427 ] Bruce Bartell commented on ENERGYINTEROP-630: --------------------------------------------- There may be all sorts of reasons why implementors may need to extend the payload content. I don't think allowing a VTN to communicate across the ESI would be one of those reasons. Suggest that we change the terminology to something a little more generic for extensions. Remove the example from the text of communicating with an application in the ESI. > 5.2.2 Application Specific Extensions appear to violate the statement on 475 on no direct interaction across the ESI. > --------------------------------------------------------------------------------------------------------------------- > > Key: ENERGYINTEROP-630 > URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-630 > Project: OASIS Energy Interoperation TC > Issue Type: Bug > Components: spec > Reporter: Edward Cazalet > Assignee: William Cox > Fix For: wd33 > > > 5.2.2 Application Specific Extensions - clearly is a violation of the statement on 475 of no direct interaction across the ESI. If the Application were just a VEN inside the ESI to the VTN at the ESI would we need Application Specific Extensions? -- 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]