Review Current Usage and Customer Entity Classes to ensure they match their ESPI Schema XSD files #28
Open
Review Current Usage and Customer Entity Classes to ensure they match their ESPI Schema XSD files#28
2 of 2 issues completed
Description
ESPI Usage Definition Issues
The following Usage Entity files extend IdentifiedObject, but extend Object in the ESPI Usage schema:
| Entity | Current Definition | Schema Definition |
|---|---|---|
| AggregatedNodeRefEntity | IdentifiedObject | Object |
| BatchListEntity | IdentifiedObject | BatchListType |
| IntervalReadingEntity | IdentifiedObject | Object |
| LineItemEntity | IdentifiedObject | Object |
| PnodeRefEntity | IdentifiedObject | Object |
| ReadingQualityEntity | IdentifiedObject | Object |
| RetailCustomerEntity | IdentifiedObject | Not defined by ESPI |
| ServiceDeliveryPointEntity | IdentifiedObject | Object |
The above-listed Entities are not ESPI Resources and therefore should not be wrapped in Atom Protocol statements but should be emitted as elements of an existing ESPI Resource. Consequently, they should be associated collections within their related ESPI Resources.
The BatchListEntity is a standalone XML message and not related to any ESPI Resource.
Reverting the above not to extend IdentifiedObject will affect the following directories and classes: