ID element for proposal does not correspond to VO-DML definition

[pahjbo]

The element used for the proposal identifier (id) https://github.com/opencadc/caom2tools/blob/ad1a21ec6106a10969a85d679605051f4963921a/caom2/caom2/tests/data/SampleDerived-CAOM-2.5.xml#L18

does not correspond to the VO-DML definition (proposalID) https://www.opencadc.org/caom2/#Proposal

[pdowler]

Yes, there is an inconsistency between the vodml-id and downstream (xsd and code).

I will likely hold off on fixing this until I can fully grok and figure out a plan to reconcile (or object to) ivoa/vo-dml#18 because I already noted that the vodml-id(s) and the utype(s) in tap_schema use two different styles.

[pdowler]

If I understand the BNF of the proposed rule, the vodml-id of the offending attr must be: Proposal.proposalID (or Proposal.id if fixing the vodml-id is less painful) while in the tap_schema I have this utype: caom2:Observation.proposal.id.

I've commented in ivoa/vo-dml#46 with more general details.

[pahjbo]

actually given that vodml-id has been allowed the be arbitrary then it is the <name> element that is used in forming things like xml element names

[pdowler]

WD model changed to use Proposal.id so the xsd and database column name are now "correct".