Two ways to set an IVO-ID to Creator and Contact

[gmantele]

According to section 3.1.2, the IVO-ID of a Creator and Contact can be provided in two ways:

1. by using the attribute ivo-id of vr:Creator/Contact
2. by using the ivo-id of the mandatory element name of vr:Creator/Contact.

• What's the difference between both?
• What happens if both are provided but different?
• Should we deprecate the attribute ivo-id of vr:Creator/Contact and set the IVO-ID only in the element name?

[msdemlei]

On Fri, Jan 31, 2025 at 06:11:11AM -0800, Grégory Mantelet wrote: According to section 3.1.2, the IVO-ID of a _Creator_ and _Contact_ can be provided in two ways: 1. by using the attribute `ivo-id` of vr:Creator/Contact 2. by using the `ivo-id` of the mandatory element `name` of vr:Creator/Contact. - What's the difference between both? - What happens if both are provided but different? - Should we deprecate the attribute `ivo-id` of vr:Creator/Contact and set the IVO-ID only in the element `name`?

I cannot say why an ivo-id attribute was added to vr:Creator and vr:Contact when vr:ResourceName (which is the type of the name element) has an ivo-id, too. In both cases, there can only be one name per Contact or Creator, so you'll have 1:1 on ivo-id and entity. So, I'd consider the ivo-id attributes on the embedding types an accident (presumably predating making name a vr:ResourceName), and I agree we should deprecate these attributes in the next version of VOResource.