Subject terms

[BaptisteCecconi]

In section 2 and appendix A of the document, the subject terms are not conforming to the VOResource specification, which states that the terms should come from the IVOA UAT vocabulary.

In section 2:

    <subject>Virtual observatory</subject>
    <subject>Standards</subject>
    <subject>HiPS</subject>

In appendix A:

    <subject>   software standard   </subject>
    <subject>   virtual observatory   </subject>

Definition is VOResource for the element: The content of subject SHOULD be the fragment identifier of the URI of a concept in the IVOA UAT (http://www.ivoa.net/rdf/uat/), that is, a string like "virtual-observatories".

Are we ok with this nonconformity?

[msdemlei]

On Wed, Jan 28, 2026 at 09:15:59PM -0800, Baptiste Cecconi wrote: BaptisteCecconi created an issue (ivoa-std/StandardsRegExt#15) Definition is VOResource for the <subject> element: *The content of subject SHOULD be the fragment identifier of the URI of a concept in the IVOA UAT (http://www.ivoa.net/rdf/uat/), that is, a string like "virtual-observatories".* Are we ok with this nonconformity?

I, for one, am not. Of course, it has historical reasons, as this was written even before with thought about adopting the UAT. I would certainly welcome PRs to fix this; almost all our other StandardsRegExt records are "bad" in this sense, too, and if someone were to comb through them (most of them are now in their standards' github repos, but for a quick overview you would probably just use <http://dc.zah.uni-heidelberg.de/wirr/q/ui/fixed?field0=restype&operator0=%3D&operand0=vstd%3Astandard>) and fix them, this could have the useful side effect that we could figure out a few new concepts for the data processing branch of the UAT. Am I unhappy enough about this to do the combing myself? I don't think so. Should we at least fix this in StandardsRegExt? Yes, and I'm asking myself how I could miss this in the recent review. Incidentally, teaching vocabulary checks to the RofR validator would also be very meritorious. I have some preliminary code for that, but figuring out where to put it in https://github.com/ivoa/rofr.ivoa.net took more time than I was willing to spend back then.