VOResource 1.1 RFC

[Baptiste Cecconi]

Hi all, 

I take the opportunity of Sarah's email to send also a few words about VOResource. 

The Creator and Contact of VOResource elements both include an ivo-id attribute to be used for referring to contact/creator details already declared in the registry. This is also present in the VOEvent data model and it could be useful in many other cases. This allows to keep track of personal detail changes (email, phone…) in existing resources without editing the resource itself. I couldn't find any real-world implementation of this VOResource feature. Any example out there? I'm interested to see how to declare such a resource. 

This is already implemented in other registries (such as SPASE for instance). It would be a charge to the naming authority to maintain its own Person-VOResource descriptors, but I think this is fully acceptable.

Cheers
Baptiste

 
> Le 7 juin 2017 à 16:54, Sarah Weissman <sweissman at stsci.edu> a écrit :
> 
> Hi Markus, all,
>  
> I went to the wiki to leave comments. but the registration page says “Registration has been disabled” so it looks like I can’t create an account. Please let me know if registration is enabled again and I can add the comments below there. My name is Sarah Weissman and I am a software engineer who works with Theresa Dower on the registry at STScI.
>  
> My comment is about the connections between DataCite and the new VOResource schema. Is the goal that one should be possible to map between the two standards? One limitation that I have noticed with DataCite and compatibility with astronomy data resources is with the relatedIdentifiers type. In DataCite, a relatedIdentifier must have a relatedIdentifierType associated with it, which come from a fixed list. In VOResource there is the vr:relationship type, which has a relatedResource element that appears to always be a vr:ResourceName, which as I understand it is always an IVOA identifier URI. This represents an incompatibility with DataCite in two ways. One, an IVOA identifier URI is not one of the types in the relatedIdentifierType enumeration in DataCite. Two, DataCite allows a wider range of types of identifiers that may be related to the current described resource. Has there been any thought of trying to get astronomy-specific identifier types into the allowed list for DataCite or of expanding the types of identifiers that can be specified as a relatedResource for the vr:relationship type in the VOResource schema?
>  
> We have run into this issue with DataCite with our new DOI service at MAST, where we would like to put CAOM observation IDs into the relatedIdentifiers list, and there is not an obvious way to do this, but I imagine this could be an issue for anyone who is trying to translate between any type of astronomy resource metadata and DataCite.
>  
> Thanks,
> Sarah
>  
>  
> From: <interop-bounces at ivoa.net> on behalf of Markus Demleitner <msdemlei at ari.uni-heidelberg.de>
> Date: Thursday, June 1, 2017 at 10:24 AM
> To: "interop at ivoa.net" <interop at ivoa.net>
> Subject: VOResource 1.1 RFC
>  
> Dear IVOA community,
>  
> After VOResource 1.1 went to Proposed Recommendation in April, I am
> happy to formally open the RFC for it.
>  
> Please review the text and comment on
> http://wiki.ivoa.net/twiki/bin/view/IVOA/VOResource11RFC <http://wiki.ivoa.net/twiki/bin/view/IVOA/VOResource11RFC>
>  
> In particular operators of publishing registries and authors of
> advanced registry records are cordially invited to read the document
> and ideally already provide implementation feedback; VOResource 1.1
> features can already be used, including for discovery with searchable
> registries implementing an (early) draft of RegTAP 1.1.
>  
> The RFC period ends on July 15th; it would be wonderful if reviews
> could be in by then.
>  
> Thanks,
>  
>         Markus Demleitner 
>  
> (doubling here as Registry Chair and VOResource 1.1 Editor)
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/interop/attachments/20170607/125f5095/attachment-0001.html>