rchenatjpl

Is there a better way to see the version? I wish the program would persist rather than go away when the window with the "bad" input is closed. 

In case the previous attachments didn't come through, here's a zip of them [Archive.zip](https://github.com/NASA-PDS-Incubator/pds-view/files/3780864/Archive.zip)

This sounds good. I hadn't thought to check this before.

Is this a fail? product_observational references a target not referenced in bundle or collection. validate flags the bundle but not the collection. Much more subtle: the collection references a target...

It's probably a fail. The revised test has these lid_references to targets: bundle: saturn narvi collection: saturn titan data: saturn narvi % validate -R pds4.bundle -t val69b PDS Validate Tool...

[val69b.zip](https://github.com/NASA-PDS/validate/files/7414107/val69b.zip)

@qchaupds @jordanpadams Another probable point of failure: context products all have LIDs urn:*:*:context:..., i.e. look for "context". The attached should generate no warnings or errors. % validate -R pds4.bundle -t...

[secondary.zip](https://github.com/NASA-PDS/validate/files/4790859/secondary.zip)

@jordanpadams Hi, where's the version of validate that I should test? I downloaded from https://github.com/NASA-PDS/validate/releases/tag/v2.2.1-SNAPSHOT and it's passing both of Dick's .xml files. % validate-2.2.1-SNAPSHOT/bin/validate -V gov.nasa.pds:validate Version 2.2.1-SNAPSHOT Release...

I just ran into the telescope sub-issue. The schema for Telescope (unlike Instrument) has no name or type, so presumably that's why those fields are N/A. Not sure how you...