-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: CTSPR01
-
Fix Version/s: None
-
Component/s: cts
-
Labels:
-
Environment:
-
Resolution:
Page: 41, Line: 604 -> How is the transaction ID defined? Some of these tables like 8-2 and 9-2 should specify the data type of each attribute.
Field | Original Value | New Value |
---|---|---|
Component/s | cts [ 14726 ] | |
Affects Version/s | CTSPR01 [ 17662 ] |
Status | New [ 10000 ] | Open [ 1 ] |
Environment | https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00003.html Rolando Herrero |
Rolando Herrero https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00003.html
|
Priority | Minor [ 4 ] | Major [ 3 ] |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Labels | ARCH-CONF |
Assignee | William Cox [ williamcox ] | Toby Considine [ toby.considine ] |
Resolution |
The underlying types are usually implemented as UIDs. The scope of uniqueness is a Marketplace.
A future version should include descriptive text on the Energy Interoperation 1.0 IDs and their simplification in CTS. |
Status | Resolved [ 5 ] | Applied [ 10002 ] |
Status | Applied [ 10002 ] | Closed [ 6 ] |
Missing section in CTS...The CTS profile is missing the simplification of the Energy Interoperation ID Types - see http://docs.oasis-open.org/energyinterop/ei/v1.0/os/energyinterop-v1.0-os.html#_Toc388604005 figures and text.
Integrate the CTS subset of IDs (all derived from UID) to the specification.