[towards UcdList 1.5] comments welcome on meta.ref.pid VEP-UCD-006

[Yan Grange]

Hi Mireille (et al),

So I think I agree with you that persistency does not necessarily add 
more information.

Maybe the argument of having meta.ref.ivoid, meta.ref.epic, 
meta.ref.orcid, meta.ref.handle, etc.. as primaries actually makes 
sense. I think the reason I disliked that was that it would add a sheer 
infinite amount of primaries but that argument may be purely aesthetic.

Cheers,

Yan

On 17/01/2022 15:11, Mireille LOUYS wrote:
>
> Sorry , I just add here the reference to the VEP-UCD proposed by Yan 
> on this .
>
> check https://wiki.ivoa.net/twiki/bin/view/IVOA/UCDList_1-5_RFM 
> VEP-UCD-006
>
> --------------------------------------------------------------------------------------------
>
> Hi Semantics ,
>
> I believe more discussion is needed for the organisation of the 
> meta.ref branch in the UCD tree.
>
> My question is :
>
>     Do we need the /http://meta.ref.pid 
> <http://mailsweeper.astron.nl:32224/?dmVyPTEuMDAxJiYzMTQ3YjIzYzgzY2UwY2I2Nj02MUU1Nzk5QV85ODAxXzE3NDk5XzEmJjRlNzhkNGE0M2NjM2U3NT0xMjMzJiZ1cmw9aHR0cCUzQSUyRiUyRm1ldGElMkVyZWYlMkVwaWQ=>/ 
> branch? which usage does it serve not covered by more precise types of 
> ids?
>
> The role of the UCD should be to classify the role, usage of the 
> metadata element tagged with this ucd string.
>
> Then Ucds as///http://meta.ref.xxx 
> <http://mailsweeper.astron.nl:32224/?dmVyPTEuMDAxJiYzMTQ3YjIzYzgzY2UwY2I2Nj02MUU1Nzk5QV85ODAxXzE3NDk5XzEmJjRlNzhkNGE0M2NjM2U3NT0xMjMzJiZ1cmw9aHR0cCUzQSUyRiUyRm1ldGElMkVyZWYlMkV4eHg=>/ 
> sorts of ids do the job when the xxx kind can be resolved with a 
> specific process.
>
> If we use http://meta.ref.pid 
> <http://mailsweeper.astron.nl:32224/?dmVyPTEuMDAxJiYzMTQ3YjIzYzgzY2UwY2I2Nj02MUU1Nzk5QV85ODAxXzE3NDk5XzEmJjRlNzhkNGE0M2NjM2U3NT0xMjMzJiZ1cmw9aHR0cCUzQSUyRiUyRm1ldGElMkVyZWYlMkVwaWQ=> 
> , we can just infer it is an identifier which is persistent , but 
> can't decide where and how to resolve it.
>
> On the contrary, each meta.ref.ivoid, meta.ref.epic, meta.ref.orcid, 
> meta.ref.handle, etc... indicate already which sort of service will 
> resolve them.
>
>
> /meta.ref/ in the ucd tree already conveys the idea of a persistent 
> identifier, I guess, because if it would not be persistent, I would 
> not cite it in a an archive metadata record.
>
> Am I forgetting something here ? any use case where pid cannot be 
> specified more precisely with a specializedid as the ones above ?
>
>
> cheers, Mireille
>
> -- 
> --
> Mireille Louys,  MCF (Associate Professor)
> Centre de données CDS		IPSEO, Images, Laboratoire Icube
> Observatoire de Strasbourg	Telecom Physique Strasbourg
> 11 rue de l'Université		300, Bd Sebastien Brandt CS 10413
> F- 67000-STRASBOURG		F-67412 ILLKIRCH Cedex
> Tel: +33 3 68 85 24 34

-- 
My working schedule likely differs from yours. Do not feel compelled to read or reply to my email(s) outside your office hours.
Dutch and English are both ok to me.

Yan Grange
SDC software developer
ASTRON
het Nederlands instituut voor radioastronomie
the Netherlands Institute for Radio Astronomy
Oude Hogeveensedijk 4
Kamer/room 1.58
7991 PD, Dwingeloo
Nederland/The Netherlands
Tel.: (+31) (0)521595796
Fax : (+31) (0)521595101
Skype: ygg-skypename

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x179F1A7582E36D64.asc
Type: application/pgp-keys
Size: 6974 bytes
Desc: OpenPGP public key
URL: <http://mail.ivoa.net/pipermail/semantics/attachments/20220117/40c07875/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://mail.ivoa.net/pipermail/semantics/attachments/20220117/40c07875/attachment.sig>