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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emix message

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


Subject: [OASIS Issue Tracker] Commented: (EMIX-510) PAP03 Req #39: apparentgap; environmental, possible flicker errors



    [ http://tools.oasis-open.org/issues/browse/EMIX-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26952#action_26952 ] 

Aaron Snyder  commented on EMIX-510:
------------------------------------

let's look at the specification, to see how the environmental warrants are defined (section 15.1):
Environmental Warrant: Quantifies the environmental burden created during the generation of the electric power.

let's look at the schema (emix-warrants.xsd) to see how that warrant quantifies the environmental burden:
	<xs:complexType name="EnvironmentalWarrantType" abstract="true" mixed="false">
		<xs:annotation>
			<xs:documentation>An Environmental Warrant asserts what environmental cost was created by the product.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="emix:BaseWarrantType">
				<xs:sequence>
					<xs:element ref="emix:product" minOccurs="1" maxOccurs="unbounded"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>

with the warrant itself, there is no actual definition of anything. it is an empty bucket with an extension to emix:product

so, let's go look at emix:product (emix.xds) to see the quantification of the environmental burden:
	<!-- 1.1 EMIX Product -->
	<xs:element name="product" type="emix:ProductType">
		<xs:annotation>
			<xs:documentation>Emix Product, .i.e., a Product Description applied to a schedule.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="ProductType" mixed="false">
		<xs:annotation>
			<xs:documentation>EMIX Product Type, i.e. a Product Description applied to a Schedule</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="emix:EmixBaseType">
				<xs:sequence>
					<xs:element ref="emix:transactiveState"/>
					<xs:element ref="emix:expirationDate" minOccurs="0" maxOccurs="1"/>
					<xs:element ref="emix:integralOnly" minOccurs="0" maxOccurs="1">
						<xs:annotation>
							<xs:documentation>As part of a Tender, indicates element must be accepted in full or rejected</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="emix:currency"/>
					<xs:element ref="emix:marketContext"/>
					<xs:element ref="emix:side"/>
					<xs:element ref="emix:terms"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>

we can keep digging, but i fail to see either (1) a quantification of the environmental burden or (2) a powerful information model for communication of environmental attributes, as the environmental warrant is actually a proverbial empty bucket. maybe some more illumination can be provided on where exactly the "quantification" occurs or where the information model actually resides.

it does not seem that we can accept that the constructs in the specification and the emix-warrants.xsd are actually providing the definitions of these warrants, i.e., source, quality, content, environmental, controllability, when all they appear to be are containers for emix:producttype, itself devoid of some of the elements needed to actually define them.

i recommend this issue remain open.

> PAP03 Req #39: apparent gap; environmental, possible flicker errors
> -------------------------------------------------------------------
>
>                 Key: EMIX-510
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-510
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Sub-task
>    Affects Versions: CSD03/PR03
>         Environment: Aaron Snyder
>            Reporter: Aaron Snyder 
>            Assignee: William Cox
>
> Requirement Text:
> Product characteristics shall include delivery schedule, quality (reliability, power quality, source), and environmental and regulatory characteristics.
> Apparent Gaps:
> Environmental characteristics are not in the specification. Limited power quality. Some errors in PQ flicker measurement representations.

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