[sc34wg3] Re: [RDFTM] Guidelines: Editor's draft for review
Bernard Vatant
sc34wg3@isotopicmaps.org
Fri, 10 Feb 2006 16:27:19 +0100
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Arial" size="-1">Hi Steve, and all RDFTM'ers<br>
<br>
First : Good job, congratulations!<br>
<br>
A first comment, guess what, on the section on identity :))<br>
</font>
<blockquote><font face="Arial" size="-1"><a>(1) If the topic has one or
more subject identifiers and no subject locators, one subject
identifier (chosen at random) becomes the URIref of the resource.
Additional subject identifiers become owl:sameAs properties.</a><br>
</font></blockquote>
<font face="Arial" size="-1">And in the final section on
non-deterministic rules<br>
</font>
<blockquote>
<p><font face="Arial" size="-1"><a>(2) Topics with multiple
identifiers — because there is no deterministic way to choose the
identifier to use as the URIref of the resulting resource.<br>
</a></font></p>
</blockquote>
<font face="Arial" size="-1">I would say that this is a contrario a
completely deterministic situation. <br>
<br>
TM2RDF : A topic with several subject identifiers should map to *one
RDF resource per subject identifier*, those being linked to each other
by owl:sameAs relationships. There is no choice to be made (random or
not) of one URIref over another. Actually there is one single resource,
but chosing one URIref as an arbitrary "preferred one" so to speak,
does not make much sense. </font><font face="Arial" size="-1"><a>Does
this rule break the general principle "one TM subject = one RDF
resource"? I don't think so, since resources linked by </a><a>owl:sameAs
properties just seem to be different because they have distinct URIref,
but are actually one single resource.
http://www.w3.org/TR/owl-ref/#IndividualIdentity is crystal clear about
that.</a></font><br>
<font face="Arial" size="-1">I suppose you are well aware of the
consequences in terms of the resulting species of OWL, of this
systematic use of owl:sameAs. If the resources generated are classes or
properties, they will also be individuals due to the semantics of
owl:sameAs, so you are in OWL-Full. What about a possible escape rule
in that case, which would be to generate owl:equivalentClass or
owl:equivalentProperty predicates instead of owl:sameAs? Did you
discuss this option? <br>
<br>
RDF2TM : When two (or more) (individual) resources are linked by a <a>owl:sameAs
property, they generate a single topic bearing the URIref of those
resources as subject identifiers. <br>
Same question as above. How many topics do you generate from resources
linked by owl:equivalentClass or owl:equivalentProperty?<br>
</a></font>
<p><font face="Arial" size="-1">Best<br>
</font></p>
<p><font face="Arial" size="-1">Bernard</font><br>
</p>
<br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.2900.2802" name="GENERATOR">
<font size="2">
<div align="left">
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><strong><span
style="font-size: 11pt; color: gray; font-family: Arial;">Bernard
Vatant</span></strong></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span
style="font-size: 10pt; color: gray; font-family: Arial;"></span><span
style="font-size: 11pt; color: gray; font-family: Arial;"><o:p><font
size="2">Knowledge Engineering</font></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span
class="important1"><b><span
style="font-size: 11pt; font-family: Arial;" lang="EN"><font
color="#901b3f">Mondeca<span class="901565122-29122005"> </span></font></span></b></span><b><span
style="color: navy; font-family: Arial;"><br>
</span></b><span
style="font-size: 10pt; color: gray; font-family: Arial;">3, cité
Nollez 75018 Paris <st1:place w:st="on"><st1:country-region w:st="on">France</st1:country-region></st1:place><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span
style="font-size: 10pt; color: gray; font-family: Arial;" lang="EN-GB">Tel.
+33 (0) 871 488 459 </span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span
style="font-size: 10pt; color: gray; font-family: Arial;" lang="EN-GB">Mail:
</span><span style="font-size: 10pt; color: gray; font-family: Arial;"><a
href="mailto:bernard.vatant@mondeca.com"><span
style="color: gray; text-decoration: none;" lang="EN-GB">bernard.vatant@mondeca.com</span></a></span><span
style="font-size: 10pt; color: gray; font-family: Arial;" lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span
style="font-size: 10pt; color: navy; font-family: Arial;"><font
color="#000000">Web: </font><a href="http://www.mondeca.com"><span
style="color: navy;" lang="EN-GB">www.</span><span style="color: navy;">mondeca.com</span></a></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span
style="font-size: 10pt; color: navy; font-family: Arial;"><font
color="#000000">Blog : <a href="http://universimmedia.blogspot.com">universimmedia.blogspot.com</a>
</font></span></p>
</div>
</font></div>
<br>
<br>
Steve Pepper a écrit :
<blockquote cite="midFOEHKIENIPCJNPNFKGJNEEFDLNAC.pepper@ontopia.net"
type="cite">
<div><span class="095201810-10022006"><font face="Arial" size="2">I
am pleased to announce the availability of the first draft of the <strong>Guidelines
for RDF/Topic Maps Interoperability</strong> for review by the SWBPD
Working Group and the ISO Topic Maps Working Group:</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2"> <a
href="http://www.ontopia.net/work/guidelines.html">http://www.ontopia.net/work/guidelines.html</a></font></span></div>
<div><span class="095201810-10022006"><font face="Arial" size="2"> <a
href="http://www.ontopia.net/work/guidelines.pdf">http://www.ontopia.net/work/guidelines.pdf</a></font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">The
next meeting of the editors is scheduled for February 21st and we would
be grateful for as much feedback as possible before then.</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">The
current draft is essentially complete, except for a number of issues
(all clearly marked in the document), and the section on the formal
specification of the translation rules (<strong>5. Translation
guidelines: formal rules</strong>). We have not yet settled on a
formalism, so we would appreciate input on (1) whether we really need
one (perhaps section<strong> 3. Informal Guidelines</strong> is
sufficient), and (2) what formalism the WGs think might be appropriate.</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">In
addition to comments on the details of the translation rules, the
examples, and the general approach, we would like feedback on whether
the SWBPD thinks this document should aim to become a <font
color="#ff0000">Recommendation</font> or just a Note. My personal
opinion is that status as a Recommendation would do a lot to enhance
the "prestige" of the Guidelines and thus encourage wider adoption.</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">I
would like to draw the attention of members of the <font
color="#ff0000">OEM Task Force</font> to section <strong>3.6.2 N-ary
relationships</strong> in particular. As you will see, we have based
our approach on the work done by Natasha, Alan and Pat in the document <em>Defining
N-ary Relations on the Semantic Web </em>(latest draft at <a
href="http://smi-web.stanford.edu/people/noy/nAryRelations/n-aryRelations-2nd-WD.html">http://smi-web.stanford.edu/people/noy/nAryRelations/n-aryRelations-2nd-WD.html</a>).
It seems to us that we only need to define a single class (which we
have called <font face="Courier New">rdftm:N-aryProperty</font>, for
consistency with the rest of the RDFTM Guidelines) in order to <strong>both</strong>
represent Pattern 1 (A and B) <strong>and</strong> provide the
guidance necessary to achieve RDFTM interoperability. We would
appreciate your feedback on this.</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">The
work of the editors has been taking place using the University of
Bologna Wiki at <a
href="http://tesi.fabio.web.cs.unibo.it/cgi-bin/twiki/bin/view/RDFTM">http://tesi.fabio.web.cs.unibo.it/cgi-bin/twiki/bin/view/RDFTM</a>.
Minutes of our conference calls are available at <a
href="http://tesi.fabio.web.cs.unibo.it/RDFTM/MinutesOfConferenceCalls">http://tesi.fabio.web.cs.unibo.it/RDFTM/MinutesOfConferenceCalls</a>.</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">We
look forward to receiving your comments.</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">Finally,
let me take this opportunity to apologize for my lack of active
participation in the SWBPD WG during the last months: I have been off
sick for quite a while. I will try to ensure that at least one of the
RDFTM editors participates in WG telecons from now on.</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">Best
regards,</font></span></div>
<div><span class="095201810-10022006"></span> </div>
<div><span class="095201810-10022006"><font face="Arial" size="2">Steve</font></span></div>
<p><font size="2">--<br>
Steve Pepper <a class="moz-txt-link-rfc2396E" href="mailto:pepper@ontopia.net"><pepper@ontopia.net></a><br>
Chief Strategy Officer, Ontopia<br>
Convenor, ISO/IEC JTC 1/SC 34/WG 3<br>
Editor, XTM (XML Topic Maps 1.0)<br>
</font></p>
</blockquote>
</body>
</html>