MIVOT: fully qualified attribute names

[Paul Harrison]

Hi Mark,



> On 7 Mar 2023, at 17:59, CresitelloDittmar, Mark <mdittmar at cfa.harvard.edu> wrote:
> 
> All,
> 
> I'm just coming off of leave, and catching up on this thread.
> A couple quick thoughts:
>  
> > PH: "I can follow all of  Std&Doc rules and all of the VO-DML std rules and produce PhotDM 1.2 with entirely different VODML-IDs - It is not sensible, but it is legal,"
> A version 1.2 of the model with completely different VODML-IDs would not be considered backward compatible, so not qualify as a 1.2.
> I suppose it would be true that a V2.0 of the model could have completely different VODML-IDs defined.

If you concede that they could be different for a major version then my argument still holds.
> 
> > PH: "Once it is agreed that the VODML-IDs are UTypes then they can be dropped entirely as they are mechanically created from the model structure"
> VODML-IDs are not the same as UTypes, they do not change due to context as UTypes do.  A "coords:TimeFrame.timescale" does not change when used within a Cube, TimeSeries, Mango, etc. instance.
> 
> Do I have this correct?  The convention of generating VODML-IDs as "<ClassName>.<attribute name>" has created the perception that they are redundant with the actual attribute name when used to identify the role of the item in MIVOT annotation.
> 
> 

Whether they are UTypes or not is irrelevant to my argument - I have never understood what a UType is anyway.

The real point is that the VODML-ID "coords:TimeFrame.timescale” could be "coords:a.b" according to the VO-DML standard - there is no connection between the vodml-id and the name of the model element as defined in the standard - I want to make the connection, and once the connection is made, the VODML-ID is redundant as it can be generated from the model structure.

Paul



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2893 bytes
Desc: not available
URL: <http://mail.ivoa.net/pipermail/dm/attachments/20230307/b012ca54/attachment.p7s>