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-517) Use of ApplicableLocation in eiDistributeQuote


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

William Cox updated ENERGYINTEROP-517:
--------------------------------------

    Affects Version/s: CSD02/PR02
           Resolution: Change name of EiDistributueQuotePayload::applicableLocation to emixInterface: emix:EmisInterfaceType.

Changed version to wd28 (the Payloads.xsd has changed in various ways since PR02, but not in this area).

In wd28+ (with payload updates) the type for applicableLocation is emix:EmixInterfaceType which allows what is requested - geospatial, ServiceDeliveryPoint, etc.

So applicableLocation refers to the substitution group.  the name should be emixInterface: emix:EmixInterfaceType.

> Use of ApplicableLocation in eiDistributeQuote
> ----------------------------------------------
>
>                 Key: ENERGYINTEROP-517
>                 URL: http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-517
>             Project: OASIS Energy Interoperation TC
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: CSD02/PR02
>         Environment: Bartell
>            Reporter: Bruce Bartell
>            Assignee: William Cox
>            Priority: Minor
>             Fix For: wd29
>
>
> The way it is structured now I only seem to be able to access gml:AbstractFeature via the ServiceAreaType (datatype extends EmixInterfaceType)
> I noticed that serviceArea is part of the emixInterface substitution group. That group has ServiceDeliveryPoint, PNode, and other locations applicable to a price.
> It seems that we should use the same structure to define and extend a price location as used for event and resource locations.i.e probably make the ApplicableLocation part of the same substitution group as ServiceDeliveryPoint, Pnode, etc. And include ServiceArea (or whatever it takes to pull in the gml stuff) as part of that.
>  

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