[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (EMIX-392) Transactive State
[ http://tools.oasis-open.org/issues/browse/EMIX-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anne Hendry updated EMIX-392:
------------------------------
Proposal:
Suggest:
"Phase of a transaction process leading up to, completing a transaction, or following a transaction."
Change 'State' to 'Phase', or 'Exchange', or 'Process'.
Move some of this information, which is very important in understanding EMIX, to earlier in the specification, possibly in Section 2.5. Just leave the definitions in the table. Move the other information, for instance, the 'Definition' of 'Exercise' is not a definition, but is a good description of how Exercise fits into the other business processes.
------------------------------- New Proposal ----------------------------
Based on discussion w/ interested parties, new proposal is to replace definition of 'Transactive State' (where it is referenced in other elements, such as prd02 Tables 4-1, 4-2, 4-3) with:
"An indicator which may be included in an EMIX ProductType, EmixOptionType, TemixType, or other subtypes of EmixBaseType to indicate that the message contents may be interpreted in the context of a transactive information exchange (Indication of Interest, Tender, etc). See Section 11 for additional information on Transactive States."
Information on Transactive States will be incorporated into Section 11 (Transactive Energy Products) similar to how other enumerations are handled in the spec (along the lines of how Power Option enumerations are described in lines 810 - 813 although possibly expanded).
This removes the need for Table 4-5 (Transactive States) since that information will be in Section 11.
This also takes care of another problem which is that Section 11 and Table 4-5 both discuss Transacative States but have different lists of Transactive States. Better to keep them all in one place (avoiding duplication and consistency problems).
Also resolves another inconsistency in that this is the only enumeration that has an entire table given to it in the spec with a definition for each enumeration. No other enumerations (eg. Power Option enumerations) have definitions in the spec and no enumerations have definitions in the schema.
was:
Suggest:
"Phase of a transaction process leading up to, completing a transaction, or following a transaction."
Change 'State' to 'Phase', or 'Exchange', or 'Process'.
Move some of this information, which is very important in understanding EMIX, to earlier in the specification, possibly in Section 2.5. Just leave the definitions in the table. Move the other information, for instance, the 'Definition' of 'Exercise' is not a definition, but is a good description of how Exercise fits into the other business processes.
------------------------------- New Proposal ----------------------------
Based on discussion w/ interested parties, new proposal is to replace definition of 'Transactive State' (where it is referenced in other elements, such as prd02 Tables 4-1, 4-2, 4-3) with:
"An indicator which may be included in an EMIX ProductType, EmixOptionType, TemixType, or other subtypes of EmixBaseType to indicate that the message contents may be interpreted in the context of a transactive information exchange (Indication of Interest, Tender, etc). See Section 11 for additional information on Transactive States."
Information on Transactive States will be incorporated into Section 11 (Transactive Energy Products) similar to how other enumerations are handled in the spec (along the lines of how Power Option is described in lines 810 - 813 although possibly expanded).
This removes the need for Table 4-5 (Transactive States) since that information will be in Section 11.
This also takes care of another problem which is that Section 11 and Table 4-5 both discuss Transacative States but have different lists of Transactive States. Better to keep them all in one place (avoiding duplication and consistency problems).
Also resolves another inconsistency in that this is the only enumeration that has an entire table given to it in the spec with a definition for each enumeration. No other enumerations (eg. Power Option) have definitions in the spec and no enumerations have definitions in the schema.
> Transactive State
> -----------------
>
> Key: EMIX-392
> URL: http://tools.oasis-open.org/issues/browse/EMIX-392
> Project: OASIS Energy Market Information Exchange (eMIX) TC
> Issue Type: Improvement
> Components: model
> Environment: Anne Hendry
> Reporter: Anne Hendry
> Assignee: Toby Considine
>
> Definition says:
> "Used to aid parsing and conformance, e.g. to distinguish between different purposes for EMIX communications."
> which doesn't fully explain what a Transactive State is.
> These are actually business processes, or phases of a business process.
--
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]