<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Dear semantics and theory,<br>
<br>
Thank you very much for your feedbacks about our proposition of a
way to put theory vocabularies in the IVOA.
<pre wrap="">We would like to conclude on this topic.
In the discussions, two aspects have been mixed
1) the need to have URL on IVOA website to store vocabulary files (datalink, theory, etc …)
2) the need to have URI to define concepts.
Below we summarise the two points and propose solutions considering the discussions on the mailing list.
1. Storage of vocabulary files on the IVOA website
----------
That is where (and in which format) to store the vocabularies. The proposition from Mireille seems good, in addition it uses existing IVOA convention.
So, storing a representation of our vocabulary (say a rdf file) in ivoa.net/vocabularies/theory/skos/TheoryVocabulary-1.0-20160101.rdf
is fine.
If we were to add another representation format, we would just have to add it under a relevant segment instead of SKOS, for example JSON, XML or whatever.
2. Unique Identifiers
--------------
We need to identify the concepts in our vocabulary. To do so we would like to use URIs as ID. The nice thing about doing that is we can associate a representation (ex a SKOS XML subset, an HTML page, a .txt file, ...) with an ID (in this case an URI), which can change over time, while the ID remains unchanged.
Since these URIs will be identifiers we want them to be permanent and unique. Then we need a namespace in ivoa.net where to define permanent URIs, to be used as identifiers.
Adding a 'purl' segment to a path rooted in <a class="moz-txt-link-abbreviated" href="http://www.ivoa.net">www.ivoa.net</a> could be used, sure, the problem is that www carries representation semantic with it, that is HTML. We don't want the identifiers to be coupled with representation details, such as HTML, or SKOS, rdf or whatever. The 'purl' subdomain doesn’t carry much semantic with it and seems a perfect abstract place (namespace) where to define permanent URIs to be used as identifiers, IDs.
So we propose: purl.ivoa.net/theory/ConceptName <a class="moz-txt-link-rfc2396E" href="http://purl.ivoa.net/theory/ConceptName"><http://purl.ivoa.net/theory/ConceptName></a>
</pre>
<br>
Best regards.<br>
<br>
Nicolas Moreau<br>
<br>
<br>
Le 01/06/2017 à 10:03, Gray, Alasdair J G a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:A86916DC-699C-4DF6-A313-9B8CB24BB8B6@hw.ac.uk">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Hi
<div class=""><br class="">
</div>
<div class="">I completely agree with the idea of having a
high-level directory like vocabularies. However, after that
should we not use content negotiation to request the specific
format that we are interested. The metadata about the vocabulary
(reproduced in a human readable form on the HTML page), could
inform clients what formats are available.</div>
<div class=""><br class="">
</div>
<div class="">Best regards,</div>
<div class=""><br class="">
</div>
<div class="">Alasdair</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 31 May 2017, at 23:18, Mireille Louys <<a
href="mailto:mireille.louys@unistra.fr" class=""
moz-do-not-send="true">mireille.louys@unistra.fr</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""> <font
class="" face="Times New Roman, Times, serif">Hi Marco
, <br class="">
</font><br class="">
<font class="" face="Times New Roman, Times, serif">Thanks
for summarising this issue.</font><br class="">
<font class="" face="Times New Roman, Times, serif">There
is also a need to discover more easily where to find
the various vocabularies proposed by the Ivoa .</font><br
class="">
<font class="" face="Times New Roman, Times, serif">I
would appreciate to have a link from the IVOA document
repository page directly , to a IVOA Vocabulary page
like what we have for XML schemata, for instance.<br
class="">
</font><br class="">
<font class="" face="Times New Roman, Times, serif">Various
vocabularies already exist , in various formats and
are used in DAL( datalink, RDF, html), Registry
(VOResource litterals, CSV), Theory ( theory</font><font
class="" face="Times New Roman, Times, serif"><font
class="" face="Times New Roman, Times, serif">
vocabulary</font> RDF/SKOS )</font><br class="">
<font class="" face="Times New Roman, Times, serif">So
this page would actually redistribute the link access
to the corresponding locations .</font><br class="">
<font class="" face="Times New Roman, Times, serif">Each
of these vocabularies should be maintained in close
contact to their WG and users , and I see the role of
Semantics more as a coordinator and curator for the
long term. <br class="">
</font><br class="">
<font class="" face="Times New Roman, Times, serif">How
to organize the vocabulary tree , is still to be
decided .</font><br class="">
<a href="http://ivoa.net/rdf" class=""
moz-do-not-send="true">ivoa.net/rdf</a> <font
class="" face="Times New Roman, Times, serif">does not
mean every file in this directory should be in rdf
format but this is somewhat misleading.<br class="">
In order to allow to gather all representation formats
for some particular vocabulary, I would prefer to have
one branch for each vocabulary and the various formats
below like : </font><br class="">
<a
href="http://ivoa.net/vocabularies/datalink/rdf/datalink-1.0-20151107.rdf"
class="" moz-do-not-send="true">ivoa.net/vocabularies/datalink/rdf/datalink-1.0-20151107.rdf</a><br
class="">
<a
href="http://ivoa.net/vocabularies/datalink/csv/datalink-1.0-20151107.txt"
class="" moz-do-not-send="true">ivoa.net/vocabularies/datalink/csv/datalink-1.0-20151107.txt</a><br
class="">
...<br class="">
<a
href="http://ivoa.net/vocabularies/theory/skos/vocabForTheory-1.0-20160101.rdf"
class="" moz-do-not-send="true">ivoa.net/vocabularies/theory/skos/vocabForTheory-1.0-20160101.rdf</a><br
class="">
<a
href="http://ivoa.net/vocabularies/theory/skos/vocabForTheory-1.0-20170509.rdf"
class="" moz-do-not-send="true">ivoa.net/vocabularies/theory/skos/vocabForTheory-1.0-20170509.rdf</a><br
class="">
etc...<br class="">
and the same for registry vocabularies if needed. <br
class="">
E<font class="" face="Times New Roman, Times, serif">ach
of them could be redirected to another site as <a
href="http://purl.obspm.fr" class=""
moz-do-not-send="true">purl.obspm.fr</a> or
anyother.</font><br class="">
<font class="" face="Times New Roman, Times, serif"><br
class="">
If the curator of the vocabulary is close enough to
the users , this should work, or am I overlooking some
issue here?<br class="">
</font>
<p class=""><font class="" face="Times New Roman, Times,
serif"> my 2c for the moment, <br class="">
</font></p>
<p class=""><font class="" face="Times New Roman, Times,
serif">cheers, Mireille<br class="">
</font></p>
<p class=""><font class="" face="Times New Roman, Times,
serif"><br class="">
</font></p>
<br class="">
<div class="moz-cite-prefix">Le 19/05/2017 à 08:42,
Marco Molinaro a écrit :<br class="">
</div>
<blockquote type="cite"
cite="mid:CABiOC75=RuyRpfxQ+VDMgjCNA-+0hUJ9_DArtj-voy+0mYrSZg@mail.gmail.com"
class="">
<pre class="" wrap="">Dear Semantics,
Dear Theory,
(IVOADoc in CC)
during the session this Tuesday, in the "SKOS in VO THeory" talk, it
was proposed a change for the vocabulary for Theory VO with patterns
pointing to
<a class="moz-txt-link-freetext" href="http://purl.ivoa.net/ConceptName" moz-do-not-send="true">http://purl.ivoa.net/ConceptName</a>
Now (apart from DNS aspects that can be managed on the DNS+IVOADoc
side - that's why IVOADoc is in CC), <a href="http://ivoa.net" class="" moz-do-not-send="true">ivoa.net</a> has already a branch
<a class="moz-txt-link-freetext" href="http://www.ivoa.net/rdf/" moz-do-not-send="true">http://www.ivoa.net/rdf/</a>
that is meant to store vocabularies (Datalink one is already there).
Also, the theory vocabulary will actually physically be in Paris, i.e.
<a href="http://purl.ivoa.net" class="" moz-do-not-send="true">purl.ivoa.net</a> will simply redirect to it.
This email is to try to understand exactly how we can make this things
work together, namely:
- the <a href="http://purl.ivoa.net" class="" moz-do-not-send="true">purl.ivoa.net</a> and its redirection to Paris (but possibly it
should survive in <a href="http://ivoa.net" class="" moz-do-not-send="true">ivoa.net</a> and be used by other parties)
- the relationship between <a href="http://purl.ivoa.net" class="" moz-do-not-send="true">purl.ivoa.net</a> and <a class="moz-txt-link-abbreviated" href="http://www.ivoa.net/rdf" moz-do-not-send="true">www.ivoa.net/rdf</a>
Ideas, comments, .... are welcome, so that we can also start thinking
of DNS changes in Trieste (hosting the <a href="http://ivoa.net" class="" moz-do-not-send="true">IVOA.net</a> domain and related
DNS) and maybe in IUCAA (where the web part of the <a href="http://ivoa.net" class="" moz-do-not-send="true">ivoa.net</a> is
physically located.
I can take care of connecting with IVOADoc and <a href="http://ivoa.net" class="" moz-do-not-send="true">ivoa.net</a> sysadmins for
the technical part.
Cheers,
Marco
</pre>
</blockquote>
<br class="">
<pre class="moz-signature" cols="72">--
--
Mireille Louys
CDS 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</pre>
</div>
</div>
</blockquote>
</div>
<br class="">
<div class="">
<div class="">
<div class="" style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;">Alasdair J G Gray</div>
<div class="" style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;">Fellow of the Higher Education Academy<br
class="">
Assistant Professor in Computer Science, <br class="">
School of Mathematical and Computer Sciences <br class="">
(Athena SWAN Bronze Award)<br class="">
Heriot-Watt University, Edinburgh UK.<br class="">
<br class="">
Email: <a href="mailto:A.J.G.Gray@hw.ac.uk" class=""
moz-do-not-send="true">A.J.G.Gray@hw.ac.uk</a><br
class="">
Web: <a href="http://www.macs.hw.ac.uk/%7Eajg33" class=""
moz-do-not-send="true">http://www.macs.hw.ac.uk/~ajg33</a><br
class="">
ORCID: <a href="http://orcid.org/0000-0002-5711-4872"
class="" moz-do-not-send="true">http://orcid.org/0000-0002-5711-4872</a><br
class="">
Office: Earl Mountbatten Building 1.39<br class="">
Twitter: @gray_alasdair</div>
</div>
</div>
<br class="">
</div>
</blockquote>
<br>
</body>
</html>