VOResource 1.1 RFC

[Arnold Rots]

Ah, sorry, I thought you were here.
The LISA site has links to the posters on Zenodo. Mine is available there.

Here is the DOI:
https://doi.org/10.5281/zenodo.801569

Cheers,

  - Arnold

On Jun 7, 2017 5:27 PM, "Sarah Weissman" <sweissman at stsci.edu> wrote:

> Hi Arnold,
>
>
>
> I am not at LISA. Do you have a digital version of your poster that you
> can share?
>
>
>
> -Sarah
>
>
>
> *From: *Arnold Rots <arots at cfa.harvard.edu>
> *Date: *Wednesday, June 7, 2017 at 11:25 AM
> *To: *Sarah Weissman <sweissman at stsci.edu>
> *Cc: *"interop at ivoa.net" <interop at ivoa.net>, Markus Demleitner <
> msdemlei at ari.uni-heidelberg.de>
> *Subject: *Re: VOResource 1.1 RFC
>
>
>
> Sarah,
>
>
>
> Would the scheme that I outline in my poster here at LISA VIII resolve the
> problem?
>
>
>
>   - Arnold
>
>
>
> On Jun 7, 2017 4:56 PM, "Sarah Weissman" <sweissman at stsci.edu> wrote:
>
> 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
>
>
>
> 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/6ccfb848/attachment.html>