There are some elements in Core that are not used by any types within NIEM. While most are valid and are provided for easy use in IEPDs, the list should be reviewed to ensure that no elements were inadvertently omitted from a type or left behind during prior refactoring.
Suggested list to review from Core
ContactAbstract
Has a nc:ContactEntity substitution
Not needed by nc:ContactInformationType, which already contains nc:ContactEntity directly
Suggest removing nc:ContactAbstract as it does not seem to be needed any more
DirectionDatumCode (nga:DirectionDatumCodeType)
MilOps also defines a direction datum code element that uses the same NGA code set
Codes: geodetic, magnetic, militaryGrid, relative
The MilOps element is used in two MilOps types
MilOps seems to be a good fit for this element. Suggest keeping that one and removing the one from Core.
HazmatAbstract (abstract)
See #104 (hazmat harmonization)
InjuryTreatment (nc:TreatmentType)
Suggest adding this element to nc:InjuryType. It doesn't have enough information in it to stand on its own.
LatitudeCoordinate (nc:LatitudeCoordinateType)
Is this element needed since we also have nc:GeographicCoordinateLatitude (nc:LatitudeCoordinateType) that is used in type nc:Location2DGeospatialCoordinateType?
LongitudeCoordinate (nc:LongitudeCoordinateType)
Is this element needed since we also have nc:GeographicCoordinateLongitude (nc:LongitudeCoordinateType) that is used in type nc:Location2DGeospatialCoordinateType?
MilitarySummary (nc:MilitarySummaryType)
Is this element needed since we also have nc:PersonMilitarySummary (nc:MilitarySummaryType) that is used in type nc:PersonType?
Recommend removing nc:MilitarySummary
Recommend renaming the type from MilitarySummaryType to PersonMilitarySummaryType (the type is specific to a person's military experience and does not summarize an entire military organization).
PersonWorkLocation (nc:LocationType)
See #105. May be able to use the location under a new nc:PersonCurrentEmployment element.
LatitudeCoordinate and LongitudeCoordinate – Agreed should not be needed and should be covered under GML discussion.
MilitarySummary looks fine
PersonWorkLocation – suggestion looks fine
May need additional review
DirectionDatumCode – Is this relevant to the GML discussion? Some more discussion required
HazmatAbstract – Agree in principle, probably need more time to review/discuss issue #104 as a group
Full List From Core – Need to review, but at a minimum,the following should be included in a GML discussion:
Area (nc:AreaType)
CircularRegion (nc:CircularRegionType)
DirectionDatumCode (nga:DirectionDatumCodeType)
LatitudeCoordinate (nc:LatitudeCoordinateType)
LongitudeCoordinate (nc:LongitudeCoordinateType)
UTMCoordinateValue (nc:UTMCoordinateType)
It may also be worth having a unit of measure discussion at some point since we have Angular, Length, Tim, Temperature,Area, Velocity, and Volume measures included in core.
There are some elements in Core that are not used by any types within NIEM. While most are valid and are provided for easy use in IEPDs, the list should be reviewed to ensure that no elements were inadvertently omitted from a type or left behind during prior refactoring.
Suggested list to review from Core
ContactAbstract
DirectionDatumCode (nga:DirectionDatumCodeType)
HazmatAbstract (abstract)
InjuryTreatment (nc:TreatmentType)
LatitudeCoordinate (nc:LatitudeCoordinateType)
LongitudeCoordinate (nc:LongitudeCoordinateType)
MilitarySummary (nc:MilitarySummaryType)
PersonWorkLocation (nc:LocationType)
Full list from Core