[OASIS Issue Tracker] Commented: (EMIX-528) Price Optionality

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Toby Considine commented on EMIX-528:
-------------------------------------

Bruce:

Are you using the current schemas?

Emixbase requires almost nothing:

	<xs:element name="emixBase" type="emix:EmixBaseType"/>
	<xs:complexType name="EmixBaseType" abstract="true">
		<xs:annotation>
			<xs:documentation>
			iCalendar-derived object to host EMIX elements</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="xcal:VcalendarType">
				<xs:sequence>
					<xs:element ref="emix:uid" minOccurs="1" maxOccurs="1"/>
					<xs:element ref="emix:envelopeContents" minOccurs="0" maxOccurs="1"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>

No Terms, no Market Context, 

Perhaps you are talking of the 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" minOccurs="0" maxOccurs="1"/>
					<xs:element ref="emix:marketContext"/>
					<xs:element ref="emix:side"/>
					<xs:element ref="emix:terms" minOccurs="0" maxOccurs="1"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>

But there, the Terms collection is optional
Integral Only is optional
expirationDate is optional
currency is optional


marketContext is a URI, and remains a URI. It is used as a unique identifier.

a market context is also used to identify a set of StandardTerms. If standardTerms is null, then you have just entirely eliminated the concept of discoverability on the grid. "Never mind, here's a name, and you can call me on the phone to find out what it means" is not discoverability. StandardTerms does incldue a marketCotnextname, which can be anything you want "My favorite Tariff". That name doesn't mean anything, though.

Will review tiers in a separate comment.

> Price Optionality
> -----------------
>
>                 Key: EMIX-528
>                 URL: http://tools.oasis-open.org/issues/browse/EMIX-528
>             Project: OASIS Energy Market Information Exchange (eMIX) TC
>          Issue Type: Improvement
>          Components: schema, spec
>    Affects Versions: CSD03/PR03
>         Environment: Bruce Bartell
>            Reporter: Bruce Bartell
>            Assignee: Toby Considine
>             Fix For: wd36
>
>
> Remaining issue from EMIX-129:
> See Sept 1 Comment. Price should be optional in EmixBase etc.
> Topic of EMIX-129 addressed; that issue is closed.

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