[sc34wg3] [RDFTM] Guidelines: Editor's draft for review

Steve Pepper sc34wg3@isotopicmaps.org
Fri, 10 Feb 2006 11:45:24 +0100


This is a multi-part message in MIME format.

------=_NextPart_000_04DC_01C62E37.7AC90070
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I am pleased to announce the availability of the first draft of the Guidelines for RDF/Topic Maps Interoperability for
review by the SWBPD Working Group and the ISO Topic Maps Working Group:

   http://www.ontopia.net/work/guidelines.html
   http://www.ontopia.net/work/guidelines.pdf

The next meeting of the editors is scheduled for February 21st and we would be grateful for as much feedback as possible
before then.

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 (5. Translation guidelines: formal rules). We have not yet
settled on a formalism, so we would appreciate input on (1) whether we really need one (perhaps section 3. Informal
Guidelines is sufficient), and (2) what formalism the WGs think might be appropriate.

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 Recommendation 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.

I would like to draw the attention of members of the OEM Task Force to section 3.6.2 N-ary relationships in particular.
As you will see, we have based our approach on the work done by Natasha, Alan and Pat in the document Defining N-ary
Relations on the Semantic Web (latest draft at
http://smi-web.stanford.edu/people/noy/nAryRelations/n-aryRelations-2nd-WD.html). It seems to us that we only need to
define a single class (which we have called rdftm:N-aryProperty, for consistency with the rest of the RDFTM Guidelines)
in order to both represent Pattern 1 (A and B) and provide the guidance necessary to achieve RDFTM interoperability. We
would appreciate your feedback on this.

The work of the editors has been taking place using the University of Bologna Wiki at
http://tesi.fabio.web.cs.unibo.it/cgi-bin/twiki/bin/view/RDFTM. Minutes of our conference calls are available at
http://tesi.fabio.web.cs.unibo.it/RDFTM/MinutesOfConferenceCalls.

We look forward to receiving your comments.

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.

Best regards,

Steve
--
Steve Pepper <pepper@ontopia.net>
Chief Strategy Officer, Ontopia
Convenor, ISO/IEC JTC 1/SC 34/WG 3
Editor, XTM (XML Topic Maps 1.0)


------=_NextPart_000_04DC_01C62E37.7AC90070
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial size=3D2>I am =
pleased to=20
announce the availability of the first draft of the <STRONG>Guidelines =
for=20
RDF/Topic Maps Interoperability</STRONG> for review by the SWBPD Working =
Group=20
and the ISO Topic Maps Working Group:</FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial =
size=3D2>&nbsp;&nbsp; <A=20
href=3D"http://www.ontopia.net/work/guidelines.html">http://www.ontopia.n=
et/work/guidelines.html</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial =
size=3D2>&nbsp;&nbsp; <A=20
href=3D"http://www.ontopia.net/work/guidelines.pdf">http://www.ontopia.ne=
t/work/guidelines.pdf</A></FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial size=3D2>The =
next meeting of=20
the editors is scheduled for February 21st and&nbsp;we would be grateful =
for as=20
much feedback as possible before then.</FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial size=3D2>The =
current draft is=20
essentially complete, except for a number of issues (all clearly marked =
in the=20
document), and the section on the formal specification of the =
translation rules=20
(<STRONG>5. Translation guidelines: formal rules</STRONG>). We have not =
yet=20
settled on a formalism, so we would appreciate input on (1) whether we =
really=20
need one (perhaps section<STRONG> 3. Informal Guidelines</STRONG> is=20
sufficient), and (2) what formalism the WGs think might be=20
appropriate.</FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial size=3D2>In =
addition to=20
comments on the details of the translation rules, the examples, and the =
general=20
approach, we would like feedback on whether the&nbsp;SWBPD thinks this =
document=20
should aim to become a <FONT color=3D#ff0000>Recommendation</FONT> or =
just a Note.=20
My personal opinion is that status as a Recommendation would do a lot to =
enhance=20
the "prestige" of the Guidelines and thus encourage wider=20
adoption.</FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial size=3D2>I =
would like to draw=20
the attention of members of the <FONT color=3D#ff0000>OEM Task =
Force</FONT> to=20
section <STRONG>3.6.2 N-ary relationships</STRONG> in particular. As you =
will=20
see, we have based our approach on the work done by Natasha, Alan and =
Pat in the=20
document&nbsp;<EM>Defining N-ary Relations on the Semantic Web =
</EM>(latest=20
draft at <A=20
href=3D"http://smi-web.stanford.edu/people/noy/nAryRelations/n-aryRelatio=
ns-2nd-WD.html">http://smi-web.stanford.edu/people/noy/nAryRelations/n-ar=
yRelations-2nd-WD.html</A>).=20
It seems to us that we only need to define a single class (which we have =
called=20
<FONT face=3D"Courier New">rdftm:N-aryProperty</FONT>, for consistency =
with the=20
rest of the RDFTM Guidelines) in order to <STRONG>both</STRONG> =
represent=20
Pattern 1 (A and B) <STRONG>and</STRONG> provide the guidance necessary =
to=20
achieve RDFTM interoperability. We would appreciate your&nbsp;feedback =
on=20
this.</FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial size=3D2>The =
work of the=20
editors has been taking place using the University of Bologna Wiki at <A =

href=3D"http://tesi.fabio.web.cs.unibo.it/cgi-bin/twiki/bin/view/RDFTM">h=
ttp://tesi.fabio.web.cs.unibo.it/cgi-bin/twiki/bin/view/RDFTM</A>.=20
Minutes of our conference calls are available at <A=20
href=3D"http://tesi.fabio.web.cs.unibo.it/RDFTM/MinutesOfConferenceCalls"=
>http://tesi.fabio.web.cs.unibo.it/RDFTM/MinutesOfConferenceCalls</A>.</F=
ONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial size=3D2>We =
look forward to=20
receiving your comments.</FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial =
size=3D2>Finally, let me take=20
this opportunity to apologize for my lack of active participation in the =
SWBPD=20
WG during the last months: I have been off sick for quite a while. I =
will try to=20
ensure that at least one of the RDFTM editors participates in WG =
telecons from=20
now on.</FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial size=3D2>Best=20
regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D095201810-10022006><FONT face=3DArial=20
size=3D2>Steve</FONT></SPAN></DIV>
<P><FONT size=3D2>--<BR>Steve Pepper &lt;pepper@ontopia.net&gt;<BR>Chief =
Strategy=20
Officer, Ontopia<BR>Convenor, ISO/IEC JTC 1/SC 34/WG 3<BR>Editor, XTM =
(XML Topic=20
Maps 1.0)<BR></FONT></P></BODY></HTML>

------=_NextPart_000_04DC_01C62E37.7AC90070--