After Ed Koch, with changes:
If there's a restricted set of strings (or pre-defined strings) it should be in the specification, not only conformance.
• EIEvent.status should be of type string and have the following [restricted] values (lower case; extensibility is indicated by an "x-" prefix)
o none - meaning no event pending.
o far - meaning event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day.
o near - meaning event pending in the near future. The exact definition of how near in the future the pending event is active is dependent on the DR program
o active - The event has been initiated and is currently active.
o completed - The event has completed.
o canceled - The event has been canceled.
These predefined strings have the defined meaning, which should be inserted in the document and schemas, but it must be an extensible list.
See also ENERGYINTEROP-333 and its references for documentation of the overall solution.
After Ed Koch, with changes:
If there's a restricted set of strings (or pre-defined strings) it should be in the specification, not only conformance.
• EIEvent.status should be of type string and have the following [restricted] values (lower case; extensibility is indicated by an "x-" prefix)
o none - meaning no event pending.
o far - meaning event pending in the far future. The exact definition of how far in the future this refers is dependent upon the DR program, but typically means the next day.
o near - meaning event pending in the near future. The exact definition of how near in the future the pending event is active is dependent on the DR program
o active - The event has been initiated and is currently active.
o completed - The event has completed.
o canceled - The event has been canceled.
These predefined strings have the defined meaning, which should be inserted in the document and schemas, but it must be an extensible list.
See also ENERGYINTEROP-333 and its references for documentation of the overall solution.
Description
Try to pin down the enumerated values of EiEvent:status.