Should coverage products included in Phase 1 include interoperabilityIdentifier attributes?
If yes:
Should they be single (0..1 multiplicity) or multiple (0..* multiplicity)?
Where should they be encoded (presumably in an HDF5 attribute or HDF5 dataset at the feature instance level, depending on whether the multiplicity is 0..1 or 0..*).
There are arguments for both "yes" and "no".
This decision needs to be made soon, by 27 June. Changing product specifications later (to either add or remove it) will be difficult and would delay approval.
This was raised at the S-101PT last week and the comment from IEC was that they didn't consider the ECDIS functionality required integration with interoperability identifier.
I'm guessing, as you say, this would be added as a hard wired attribute at the feature instance level but this would require a bespoke extension for each of the Phase 1 products, documented in S-98 Annex C, as they can't be added to the feature catalogue.
Or are you thinking add it to the feature catalogue?
Either way, we would need the Phase 1 coverage products to propose this to S-98 Annex C.
Should coverage products included in Phase 1 include interoperabilityIdentifier attributes?
If yes:
There are arguments for both "yes" and "no".
This decision needs to be made soon, by 27 June. Changing product specifications later (to either add or remove it) will be difficult and would delay approval.