[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Issue Comment Edited: (EMIX-529) Collectorfor Warrant issues
[ http://tools.oasis-open.org/issues/browse/EMIX-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27179#action_27179 ]
Toby Considine edited comment on EMIX-529 at 9/5/11 5:03 PM:
-------------------------------------------------------------
Proposal for warrants:
Eliminate Content Warrant as it seems to be substantially a duplicate of Source Warrant
Eliminate Controllability Warrant, as this function, ill-defined, is now handled by enrollment in Energy Interop.
Improved general description of Warrants:
General description of Warrants:
Definition in Schema:
Warrants are "a written assurances that some product or service will be provided or will meet certain specifications" . Sellers use EMIX Warrants to provide information about the source of the energy or about its environmental characteristics. Buyers can use warrants to indicate what they wish to purchase. EMIX does not define specific warrants, although it does define base types for extension by those who wish to develop the various types of warrants.
In specification:
Warrants are specific assertions about the extrinsic characteristics of EMIX Products that may affect market pricing. Warrants are "a written assurances that some product or service will be provided or will meet certain specifications."
Parties may use warrants to exchange information about the source of the energy or about its environmental characteristics. Buyers can use warrants to indicate what they wish to purchase. EMIX does not define specific warrants, although it does define base types for extension by those who wish to develop the various types of warrants.
Some Warrants may be separable from the underlying energy. For example, a Warrant that energy is generated by a source that is certified as "green" by an authority, may be issued a "green certificate". In some markets, such a certificate can be traded separately.
The general form of a warrant is similar to that of an EMIX Product. It can vary by time, using schedules as in WS-Calendar. The Intervals in a Warrant may differ from those of the Product on the outside of the envelope. There may be zero Intervals in a Product if the unchanged product description applies to all.
Today, the information conveyed in warrants is local, and not ready for standardization. For example, in 2011 energy warranted as renewable in the Pacific Northwest can include hydropower. Energy markets in California exclude hydropower from their definition of renewable power. Credits or mandates for renewable energy in California are not met by Products warranted as renewable in the Pacific Northwest.
The Technical Committee has chosen to define a general semantic mechanism to convey warrants, without standardizing warrants in v1.0. The Technical Committee defined broad classes of warrants, any of which may be the subject of a future standardization effort.
Parties that need additional types of warrants can extend the abstract Warrant Type to create a new base type for Warrants not defined in this specification.
Warrant types defined in 1.0
Support for Price.
Support for Price was originally conceived of as potentially an array of products that support price. An example is a product description for wholesale purchase of a product, along with transport products to establish a base cost to support a contracted price. Without further definition, support for price is not restricted in this way as of 1.0, and Parties that wish to exchange price support should extend this type to meet their needs.
Quality Warrant
A Quality Warrant asserts or requires that the product be of a certain quality or better. A quality warrant includes an array of Quality Measures. The Quality Measure type is extensible to support the definition of additional quality measures.
Numerous quality measures are defined as part of the POWER schema of EMIX; parties wishing to specify EMIX extensions for other commodities and resources will want to define their Quality Measures.
Environmental Warrant
An Environmental Warrant is used to assert what environmental effects of the product. These may include emission of a chemical, or use of a scarce resource. No environmental warrants are defined in the EMIX 1.0 Schema. Parties wishing to exchange Environmental warrants should extend this type to create the environmental assertions that they require.
Source Warrant
A Source Warrant consists of assertions the sources (often meaning the technologies) of the commodity included in this product. Source often has specific regulated meaning in different jurisdictions, so no definition of Source is included in this specification. Parties that require source information should extend this type to create the source assertions that they require.
was (Author: toby.considine):
Proposal for warrants:
Eliminate Source Warrant as it seems to be substantially a duplicate of Content Warrant
Eliminate Controllability Warrant, as this function, ill-defined, is now handled by enrollment in Energy Interop.
Improved general description of Warrants:
General description of Warrants:
Definition in Schema:
Warrants are "a written assurances that some product or service will be provided or will meet certain specifications" . Sellers use EMIX Warrants to provide information about the source of the energy or about its environmental characteristics. Buyers can use warrants to indicate what they wish to purchase. EMIX does not define specific warrants, although it does define base types for extension by those who wish to develop the various types of warrants.
In specification:
Warrants are specific assertions about the extrinsic characteristics of EMIX Products that may affect market pricing. Warrants are "a written assurances that some product or service will be provided or will meet certain specifications."
Parties may use warrants to exchange information about the source of the energy or about its environmental characteristics. Buyers can use warrants to indicate what they wish to purchase. EMIX does not define specific warrants, although it does define base types for extension by those who wish to develop the various types of warrants.
Some Warrants may be separable from the underlying energy. For example, a Warrant that energy is generated by a source that is certified as "green" by an authority, may be issued a "green certificate". In some markets, such a certificate can be traded separately.
The general form of a warrant is similar to that of an EMIX Product. It can vary by time, using schedules as in WS-Calendar. The Intervals in a Warrant may differ from those of the Product on the outside of the envelope. There may be zero Intervals in a Product if the unchanged product description applies to all.
Today, the information conveyed in warrants is local, and not ready for standardization. For example, in 2011 energy warranted as renewable in the Pacific Northwest can include hydropower. Energy markets in California exclude hydropower from their definition of renewable power. Credits or mandates for renewable energy in California are not met by Products warranted as renewable in the Pacific Northwest.
The Technical Committee has chosen to define a general semantic mechanism to convey warrants, without standardizing warrants in v1.0. The Technical Committee defined broad classes of warrants, any of which may be the subject of a future standardization effort.
Parties that need additional types of warrants can extend the abstract Warrant Type to create a new base type for Warrants not defined in this specification.
Warrant types defined in 1.0
Support for Price.
Support for Price was originally conceived of as potentially an array of products that support price. An example is a product description for wholesale purchase of a product, along with transport products to establish a base cost to support a contracted price. Without further definition, support for price is not restricted in this way as of 1.0, and Parties that wish to exchange price support should extend this type to meet their needs.
Quality Warrant
A Quality Warrant asserts or requires that the product be of a certain quality or better. A quality warrant includes an array of Quality Measures. The Quality Measure type is extensible to support the definition of additional quality measures.
Numerous quality measures are defined as part of the POWER schema of EMIX; parties wishing to specify EMIX extensions for other commodities and resources will want to define their Quality Measures.
Environmental Warrant
An Environmental Warrant is used to assert what environmental characteristics for the product. No environmental warrants are defined in the EMIX 1.0 Schema. Parties wishing to exchange Environmental warrants should extend this type to create the environmental assertions that they require.
Content Warrant
A content warrant consists of assertions the sources (often meaning the technologies) of the commodity included in this product. Content often has specific regulated meaning in different jurisdictions, so no definition of content is included in this specification. Parties that require content information should extend this type to create the content assertions that they require.
> Collector for Warrant issues
> ----------------------------
>
> Key: EMIX-529
> URL: http://tools.oasis-open.org/issues/browse/EMIX-529
> Project: OASIS Energy Market Information Exchange (eMIX) TC
> Issue Type: Improvement
> Reporter: Toby Considine
> Assignee: William Cox
> Fix For: wd36
>
>
> Beingg created because it seems that all the Warrant issues are interlinked
--
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]