Validate does not allow browse products in the browse collection in the External product's Bundle

[murashinln]

Checked for duplicates

No - I haven't checked

🐛 Describe the bug

When I did validate for a bundle storing external products and associated browse products, I noticed that the browse products in the browse collection were not allowed to exist. I obtained following outputs:

FAIL: file:/nasA_hayabusa2_1/share/private/pds4/pds4_prep/2nd_submission_202008/work/murashin/hyb2_pds4_review/bundles/hyb2_nirs3_sp_ard_test/browse/collection_hyb2_nirs3_sp_ard_browse_v001.lblx (urn:jaxa:darts-ard:hyb2_nirs3_sp_ard:browse::1.0)
ERROR [error.label.schematron] line 8, 26: An archive product pds:logical_identifier must begin with one of (urn:nasa:pds:, urn:esa:psa:, urn:ros:rssa:, urn:jaxa:darts:, urn:isro:isda:, urn:kari:kpds:).
4 product validation(s) completed

FAIL: file:/nasA_hayabusa2_1/share/private/pds4/pds4_prep/2nd_submission_202008/work/murashin/hyb2_pds4_review/bundles/hyb2_nirs3_sp_ard_test/browse/data_iof_thermalcorr/proximity/hyb2_nirs3_20190613_01_l2d_v05.lblx (urn:jaxa:darts-ard:hyb2_nirs3_sp_ard:browse:hyb2_nirs3_20190613_01_l2d::1.0)
ERROR [error.label.schematron] line 11, 26: An archive product pds:logical_identifier must begin with one of (urn:nasa:pds:, urn:esa:psa:, urn:ros:rssa:, urn:jaxa:darts:, urn:isro:isda:, urn:kari:kpds:).
5 product validation(s) completed

🕵️ Expected behavior

I expected the browse products for the external products, i.e., product described as Product_External, can exist in the bundle for the external products.

📜 To Reproduce

1. unzip murashinln20251120.zip
2. validate -R pds4.bundle -t murashin-20251120/hyb2_nirs3_sp_ard_test --label-extension lblx

🖥 Environment Info

• Version of this software: 4.0.8
• Operating System: Red Hat Enterprise Linux release 9.4

📚 Version of Software Used

gov.nasa.pds:validate
Version 4.0.8
Release Date: 2025-11-06 22:35:49

🩺 Test Data / Additional context

murashin-20251120.zip

🦄 Related requirements

🦄 #xyz

⚙️ Engineering Details

No response

🎉 Integration & Test

No response

[jordanpadams]

@murashinln thanks for bringing this up. Unfortunately, this is an issue in the information model, and it is not going to be an easy fix. We will either need to move LID validation to validate software, or eliminate it altogether. Apologies for the inconvenience. Does the rest of the validation work as expected?

[murashinln]

@jordanpadams thanks. The rest of the validation works as expected.

[sophiaconover]

Steve and I will draft an SCR proposing attributes to indicate archive, archive later, annex, and other potential solutions. Steve is coordinating with Joe to present this at the next Management Council F2F at the end of January 2026.