iho-ohi / S-164-Sub-Group

Development and tracking of IHO S-164 Test datasets and user manual documentation
15 stars 2 forks source link

S-124 delivery #17

Open kusala9 opened 1 year ago

kusala9 commented 1 year ago

There was a discussion at S-100WG TSM on S-124 delivery which may require clarifications in S-98 for ECDIS use. One direct output of that discussion was the inclusion in S-100 (5.1.0) of clauses relating to cancellation updates as well as via metadata in CATALOG.XML. It was noted that NWs may require different promulgation methods. If this is the case, and it is product specific then it needs to be documented in S-98 Annex C and representative test data added to tests dealing with updates.

rmalyankar commented 1 year ago

As an S-98 issue this should be in the S-98 repository.

Also applies to others - #16, #15, #14, and aspects of #1 if not the whole issue. There is a way to transfer issues to a different repository but it requires higher level privileges.

kusala9 commented 1 year ago

I had a discussion with NIPWG chair on this recently. There are two actual issues here, availability of up to date edition 5.0.0 artifacts to use to make test data, and the delivery issues alluded to here.

I now understand edition 5.0.0 catalogues are available and can be used for creating test datasets (an S-124 dataset is required for PowerUp exchange set).

This issue, then, can be closed when S-100WG and NIPWG have agreed any clarifications at the S-100 level required to implement S-124 fully and when those clarifications are captured in S-164's tests (and, if necessary, S-98)

My understanding is that cancellation and replacement require clarification at the S-100 level and these mechanisms are required for S-124 to be able to replicate what the end user currently has in place (which is the IMO requirement, I believe). This would require datasets to be cancellable either via file-less or via cancellation updates (which is already in S-100 5.1.0 via TSM9), AND would require datasets to be able to cancel other datasets (and replace them).

So, we currently have in S-100 5.1.0

  1. CATALOG.XML is able to cancel a dataset via a DatasetDiscoveryMetadata entry
  2. Issuing of a cancellation update by the data producer

Required is the mechanism for a cancellation update to cancel another dataset, and replace it. This will be discussed by S-100WG and then any clarifications codified in S-98 (if required) and test datasets constructed for S-164.

This may require enhancments to the cancel/replace tests in S-164 (and would certainly require S-164 to test cancel/replace with S-124 as well as S-101.

kusala9 commented 1 year ago

I believe this will be discussed during NIPWG. It will be part of a broader debate on how cancellations are effected on ECDIS.

rmalyankar commented 1 year ago

That makes three places where cancellation is described: S-100, S-98, and the product specification(s).

kusala9 commented 1 month ago

Need to ensure S-98 Annex C clarifies how cancellation can work in the S-124 context (from the dataset) in addition to fileless (from CATALOG.XML) and via an update.