Schema discoverability improvements

[braingram]

There has been some renewed discussion on schema discoverability. The general idea is:

• user has an arbitrary ASDF file (with tags)
• user wants to get schemas for those tags

To take one roman tag as an example. If the file contains asdf://stsci.edu/datamodels/roman/tags/wfi_image-1.5.0 the user will need to:

• know that the rad manifest maps this tag to a schema
• consult the manifest to find the schema uri
• know that the schema is provided as part of rad

There are some breadcrumbs in the file, specifically the extension information contains:

  - !core/extension_metadata-1.0.0
    extension_class: asdf.extension._manifest.ManifestExtension
    extension_uri: asdf://stsci.edu/datamodels/roman/extensions/static-1.1.0
    manifest_software: !core/software-1.0.0 {name: rad, version: 0.29.0.dev5+g146d00f0a.d20251030}
    software: !core/software-1.0.0 {name: roman_datamodels, version: 0.30.0.dev19+g269cda656}

(ignoring the bug that the static manifest is listed, this is a known roman_datamodels issue) we have a:

• uri for the tag: asdf://stsci.edu/datamodels/roman/tags/wfi_image-1.5.0
• uri for the extension/manifest: asdf://stsci.edu/datamodels/roman/extensions/datamodels-1.6.0/asdf://stsci.edu/datamodels/roman/manifests/datamodels-1.6.0
• uri for the schema: asdf://stsci.edu/datamodels/roman/schemas/wfi_image-1.5.0

With the python library most of these uris (all except the extension uri) can all be resolved to resources using the resource manager.

This topic is to discuss if there are improvements that can be made to this process. These might include:

• improvements to bookkeeping to record additional useful information in the files
• infrastructure to allow more general uri-to-resource resolution (think dois/zenodo)
• updates to the ASDF specification to clarify/formalize the above links

Pinging @nden @perrygreenfield @eslavich @embray for visibility