You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
External products, namely, Product_Bundle and Product_Collection of type: External and Product_External should have different rules for creating valid URNs to be used as logical identifiers (LIDs) than standard archive products. The purpose of External products are to provide a clear way to register products that otherwise wouldn't be in 'official' archives. The current set of schematron rules for validating LIDs across External products requires the archive-wide set of rules, meaning LIDs must conform to the enumerated list of known archive institutions (e.g., urn:nasa:pds..., urn:esa:psa..., urn:jaxa:darts..., etc.). Furthermore, the LID formations should adhere to the standard bundle formations where bundles have 4 segments, collections have 5 segments, and products have 6 segments (implying Product_External should be expected to be a member of an external bundle and collection).
Requested Changes
Add additional schematron rules pertaining to Product_Bundle (type:External), Product_Collection (type:External), and Product_External to allow URNs that are valid if and only if the initial 3 segments are not on the enumerated list of approved archives (e.g., urn:nasa:pds..., urn:esa:psa..., urn:jaxa:darts..., etc.).
Bundle_Member_Entry/reference_type will need to have an additional value of 'bundle_has_external_collection' to be able to reference member collections to an external bundle.
Product_Bundle (type:External)
- must have 3 colons (i.e., 4 segments)
- must start with 'urn:'
- not on the enumerated list of approved archives (e.g., urn:nasa:pds..., urn:esa:psa..., urn:jaxa:darts..., etc.).
Product_Collection (type:External)
- must have 4 colons (i.e., 5 segments)
- must start with 'urn:'
- not on the enumerated list of approved archives (e.g., urn:nasa:pds..., urn:esa:psa..., urn:jaxa:darts..., etc.).
Product_External
- must have 5 colons (i.e., 6 segments or fewer).
- must start with 'urn:'
- not on the enumerated list of approved archives (e.g., urn:nasa:pds..., urn:esa:psa..., urn:jaxa:darts..., etc.).
Applicable Attachments
The enclosure contains the updates the 1M00 schematron SCH file to validate the Requested Changes:
🦄 Sibling SCR
NASA-PDS/PDS4-CCB#29
💡 SCR Summary
Problem Statement
External products, namely, Product_Bundle and Product_Collection of type: External and Product_External should have different rules for creating valid URNs to be used as logical identifiers (LIDs) than standard archive products. The purpose of External products are to provide a clear way to register products that otherwise wouldn't be in 'official' archives. The current set of schematron rules for validating LIDs across External products requires the archive-wide set of rules, meaning LIDs must conform to the enumerated list of known archive institutions (e.g., urn:nasa:pds..., urn:esa:psa..., urn:jaxa:darts..., etc.). Furthermore, the LID formations should adhere to the standard bundle formations where bundles have 4 segments, collections have 5 segments, and products have 6 segments (implying Product_External should be expected to be a member of an external bundle and collection).
Requested Changes
Add additional schematron rules pertaining to Product_Bundle (type:External), Product_Collection (type:External), and Product_External to allow URNs that are valid if and only if the initial 3 segments are not on the enumerated list of approved archives (e.g., urn:nasa:pds..., urn:esa:psa..., urn:jaxa:darts..., etc.).
Bundle_Member_Entry/reference_type will need to have an additional value of 'bundle_has_external_collection' to be able to reference member collections to an external bundle.
Applicable Attachments
The enclosure contains the updates the 1M00 schematron SCH file to validate the Requested Changes:
aaaIM_1M00_updates_20240904.zip
Added to parent epic?
Will do
The text was updated successfully, but these errors were encountered: