[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [energyinterop] Error and short-fuse comments
What? Go next door without walking around the block? The requirement is that the resource can provide, as part of the enrollment process, whatever location information that can be targeted
in an event. I would imagine that the resource has a gml point location and would know if it is inside a polygon target. I don’t know what we need to get to do that. Xtensible Solutions From: Gray, Gerald [mailto:ggray@epri.com]
My preference is to reference GML directly.
Good development of the pros/cons Toby, however, on balance I come down on the side of referencing GML directly. Referencing GML directly, if it diverges, is a single order of divergence. Referencing GML via EMIX, if there is divergence, potentially creates two orders of divergence. From: energyinterop@lists.oasis-open.org
[mailto:energyinterop@lists.oasis-open.org] On Behalf Of
Toby Considine Ok, Bruce has zoomed in on an unexpected feature of XML. This feature breaks the Resource location. See below for thread. The abstract type is inherited properly. It breaks the substitution group rules, though. To recap: <type name =”fooType” abstract=”true”> <element name=”foo” type=”fooType” > <type name =”fooType” abstract=”true”> <element name=”notFoo” type=”fooType” > <xs:element name="fooFighter" type="emix:fooFighterType" substitutionGroup="foo"/> <type name =”fooFighterType” > <xs:extension base="fooType"/> </type> <xs:element name="fooLover" type=" fooLoverType " substitutionGroup="foo"/> <type name =”fooLoverType” > <xs:extension base="fooType"/> </type> fooFIghter and fooLover are substitutes for foo fooFIghter and fooLover are NOT substitutes for notFoo We have three routes we can go.
(1)
WE can make location a name (or reference) to an existing concrete type,
(2)
we can make location a container for an EMix Interface (3)
We can simply stick an EMix Interface in there can get rid of the word Location. (4)
We can lose the entire EMIX stuff and refer to the GML directly Discussion: <element name="location"
type="emix:ServiceAreaType"/> 2) If we just put an Emix Interface there, no one will understand it. The word and concept Location is important, especially
since a Resource, could, in concept, be a collection of [devices] each with its own EMIX Interface.
<element name="location"
type="locationType> <type="locationType> <element ref="emix:emixInterface"/> </type> 3) Emix defined it. Add an annotation and be done with it. THe other interfaces (see 2) will be embedded inside emix:resources
anyway, so why worry about it. <element name="emixInterface" type="emix:EmixInterfaceType"/>
4)
We can lose the entire EMIX stuff and refer to the GML directly. It is just confusing to reference that
EMIX stuff. There would be no issue if we went directly to the GML. Well, we would have to include the gml profile defintions stuff, and it could, in concept, diverge from the normalization of GML performed in EMIX. The down-side is that if a future version
of emix defines standard gml profiles for, say “within 50 feet of a Transmission line” or “distribution zone associated with a sub-station” we will not inherit them. <element name="location" type="gml:AbstractFeature"/> Please discuss and vote tc "A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away." -Antoine de
Saint-Exupery
From: Toby Considine [mailto: OK, I see the symptom in xmlspy schema view. Not sure why, though. Let me poke around further. tc "A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away." -Antoine de
Saint-Exupery
From: Considine, Toby (Campus Services
IT) Not sure what is going on there. I will wiggle the parts and see if something squeaks. EMixInterface is, of course, abstract. It relies either on inclusion of gml schemas (for spatial references) or EMIX Power schemas
(for node/meter/etc references). Any chance those are not being resolved properly? tc "It is the theory that decides
what can be observed." - Albert Einstein
From: energyinterop@lists.oasis-open.org
[mailto:energyinterop@lists.oasis-open.org] On Behalf Of
The type shows up in the latest version, but I have to resolve it manually. Xtensible Solutions bbartell@xtensible.net |
www.xtensible.net -----Original Message----- Toby Considine commented on ENERGYINTEROP-474: ---------------------------------------------- Location is an EMix Interface... <xs:element name="location" type="emix:EmixInterfaceType" minOccurs="1" maxOccurs="1"/> > eiEnroll Resource Not in WD25 > ----------------------------- > > Key: ENERGYINTEROP-474 > URL:
http://tools.oasis-open.org/issues/browse/ENERGYINTEROP-474 > Project: OASIS Energy Interoperation TC > Issue Type: Improvement > Components: spec > Affects Versions: wd25 > Environment: Bartell > Reporter:
> Assignee: Toby Considine > Fix For: wd34 > > > The enrollment services are not in wd25 in spec or schema payloads. > Is this going to be in CD02? or later? > I am assuming that this is where the resoruce "capabilities and constraints" will be defined. > Capabilities as what can be shed/generate over time (ramps) and contraints as min/max per # items that were already defined for resoruces. --
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
--------------------------------------------------------------------- To unsubscribe, e-mail:
energyinterop-unsubscribe@lists.oasis-open.org For additional commands, e-mail:
energyinterop-help@lists.oasis-open.org |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]