[topicmapmail] XML Schema for XTM DTD

Mon, 03 Feb 2003 17:54:50 +0100

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--Boundary_(ID_nLhWHP7210JoFZ2Q6ACUfw)
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable

Couldn't the OASIS TM community *recommend* an XSD version?
There are many use cases when a schema is necessary today - do we like =
this
or not.
We should not wait until all the "rest of the standard settles out".=20

I think Max Voskob has posted a valuable draft yesterday. It looks =
quite
reasonable as a schema.
But I am not the XTM expert. Did anyone test it with a given XTM?
=20

Thomas Bandholtz
Manager KM Applications
=20
SchlumbergerSema GmbH
Kaltenbornweg 3
D50679 K=C3=B6ln / Cologne=20
Germany

Tel: +49 221 8299 264
Fax: +49 221 8299 277

EMail:   TBandholtz@slb.com
Internet: http://www.schlumbergersema.de

> -----Original Message-----
> From: Mason, James David (MXM) [mailto:masonjd@y12.doe.gov]
> Sent: Monday, February 03, 2003 5:05 PM
> To: 'Max Voskob'; topicmapmail@infoloom.com;
> topicmaps-comment@lists.oasis-open.org
> Subject: RE: [topicmapmail] XML Schema for XTM DTD
>=20
>=20
> Making XSD supersede DTD is one thing that SC34 can't do, no=20
> matter what the
> claimed capabilities of XSD. DTD is SC34's creation, so it=20
> gets automatic
> priority.=20
>=20
> Notice also that XTM is, as mentioned in several other=20
> postings, only an
> interchange format. It is not the definition of what a Topic=20
> Map is: that's
> done elsewhere and is being expanded on in other parts of the=20
> standard, some
> of which are works in progress. When the rest of the Topic=20
> Map standard
> settles out, then we can revisit interchange formats.
>=20
> Jim Mason
>=20
> James David Mason, Ph.D.
>=20
> Y-12 National Security Complex
> Bldg. 9113, M.S. 8208
> P.O. Box 2009
> Oak Ridge, TN 37831-8208 U.S.A.
> +1 865 574 6973
>=20
> Chairman, ISO/IEC JTC1/SC34
> http://www.y12.doe.gov/sgml/sc34/sc34oldhome.htm
>=20
>=20
> -----Original Message-----
> From: Max Voskob [mailto:mvoskob@msi.com.au]
> Sent: Sunday, February 02, 2003 2:29 PM
> To: topicmapmail@infoloom.com; topicmaps-comment@lists.oasis-open.org
> Subject: Re: [topicmapmail] XML Schema for XTM DTD
>=20
>=20
> DTD has more limitations than XSD.
>=20
> I'd prefer to see an XSD schema as the source of truth, DTD=20
> for those who
> are still using it and RelaxNG can also normative as long as=20
> the target XML
> document is still valid for the XSD.
>=20
> However, UDDI we will need an XSD schema of XTM for adoption.
>=20
> Cheers,
> Max
>=20
>=20
> ----- Original Message -----
> From: "Daniel L. Koger" <daniel@kogers.com>
> To: "Steve Pepper" <pepper@ontopia.net>; <topicmapmail@infoloom.com>
> Cc: "Max Voskob" <mvoskob@msi.net.nz>
> Sent: Monday, February 03, 2003 7:37 AM
> Subject: RE: [topicmapmail] XML Schema for XTM DTD
>=20
>=20
> > That would definitely have my support :)
> >
> > -----Original Message-----
> > From: Steve Pepper [mailto:pepper@ontopia.net]
> > Sent: Sun 2/2/2003 08:22
> > To: topicmapmail@infoloom.com
> > Cc: Daniel L. Koger; Max Voskob
> > Subject: Re: [topicmapmail] XML Schema for XTM DTD
> >
> >
> >
> > At 17:15 02.02.2003 +0100, Lars Marius Garshol wrote:
> > >| It is acceptable if the DTD is normative, but it would=20
> be nice to at
> > >| least have a consistent format for schema.
> > >
> > >If there is a need for an XSDL schema I agree it would be good if
> > >everyone used the same schema. One way to achieve that is=20
> to make it
> > >an informative annex to the ISO standard.
> >
> > I think this is the way to go. Have the DTD be normative and =
publish
> > an XSD "translation" as an annex.
> >
> > Steve
> >
> > --
> > Steve Pepper, Chief Executive Officer <pepper@ontopia.net>
> > Convenor, ISO/IEC JTC1/SC34/WG3  Editor, XTM (XML Topic Maps)
> > Ontopia AS, Waldemar Thranes gt. 98, N-0175 Oslo, Norway.
> > http://www.ontopia.net/ phone: +47-23233080 GSM: +47-90827246
> >
> >
> >
> >
>=20
> _______________________________________________
> topicmapmail mailing list
> topicmapmail@infoloom.com
> http://www.infoloom.com/mailman/listinfo/topicmapmail
> _______________________________________________
> topicmapmail mailing list
> topicmapmail@infoloom.com
> http://www.infoloom.com/mailman/listinfo/topicmapmail
>=20

--Boundary_(ID_nLhWHP7210JoFZ2Q6ACUfw)
Content-type: text/html; charset=utf-8
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dutf-8">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [topicmapmail] XML Schema for XTM DTD</TITLE>
</HEAD>
<BODY>

Couldn't the OASIS TM community *recommend* an XSD =
version?
 There are many use cases when a schema is necessary =
today - do we like this or not.
 We should not wait until all the &quot;rest of the =
standard settles out&quot;.

I think Max Voskob has posted a valuable draft =
yesterday. It looks quite reasonable as a schema.
 But I am not the XTM expert. Did anyone test it with =
a given XTM?
 &nbsp;

<P><FONT SIZE=3D2>Thomas Bandholtz</FONT>
<BR><FONT SIZE=3D2>Manager KM Applications</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>SchlumbergerSema GmbH</FONT>
<BR><FONT SIZE=3D2>Kaltenbornweg 3</FONT>
<BR><FONT SIZE=3D2>D50679 K=C3=B6ln / Cologne </FONT>
<BR><FONT SIZE=3D2>Germany</FONT>
</P>

<P><FONT SIZE=3D2>Tel: +49 221 8299 264</FONT>
<BR><FONT SIZE=3D2>Fax: +49 221 8299 277</FONT>
</P>

<P><FONT SIZE=3D2>EMail:&nbsp;&nbsp; TBandholtz@slb.com</FONT>
<BR><FONT SIZE=3D2>Internet: <A HREF=3D"http://www.schlumbergersema.de" =
TARGET=3D"_blank">http://www.schlumbergersema.de</A></FONT>
</P>
<BR>
<BR>
<BR>

&gt; -----Original Message-----
 &gt; From: Mason, James David (MXM) [<A =
HREF=3D"mailto:masonjd@y12.doe.gov">mailto:masonjd@y12.doe.gov</A>]</FON=
T>
 &gt; Sent: Monday, February 03, 2003 5:05 PM
 &gt; To: 'Max Voskob'; =
topicmapmail@infoloom.com;
 &gt; topicmaps-comment@lists.oasis-open.org
 &gt; Subject: RE: [topicmapmail] XML Schema for XTM =
DTD
 &gt; 
 &gt; 
 &gt; Making XSD supersede DTD is one thing that SC34 =
can't do, no 
 &gt; matter what the
 &gt; claimed capabilities of XSD. DTD is SC34's =
creation, so it 
 &gt; gets automatic
 &gt; priority. 
 &gt; 
 &gt; Notice also that XTM is, as mentioned in =
several other 
 &gt; postings, only an
 &gt; interchange format. It is not the definition of =
what a Topic 
 &gt; Map is: that's
 &gt; done elsewhere and is being expanded on in =
other parts of the 
 &gt; standard, some
 &gt; of which are works in progress. When the rest =
of the Topic 
 &gt; Map standard
 &gt; settles out, then we can revisit interchange =
formats.
 &gt; 
 &gt; Jim Mason
 &gt; 
 &gt; James David Mason, Ph.D.
 &gt; 
 &gt; Y-12 National Security Complex
 &gt; Bldg. 9113, M.S. 8208
 &gt; P.O. Box 2009
 &gt; Oak Ridge, TN 37831-8208 U.S.A.
 &gt; +1 865 574 6973
 &gt; 
 &gt; Chairman, ISO/IEC JTC1/SC34
 &gt; <A =
HREF=3D"http://www.y12.doe.gov/sgml/sc34/sc34oldhome.htm" =
TARGET=3D"_blank">http://www.y12.doe.gov/sgml/sc34/sc34oldhome.htm</A></=
FONT>
 &gt; 
 &gt; 
 &gt; -----Original Message-----
 &gt; From: Max Voskob [<A =
HREF=3D"mailto:mvoskob@msi.com.au">mailto:mvoskob@msi.com.au</A>]=

&gt; Sent: Sunday, February 02, 2003 2:29 PM
 &gt; To: topicmapmail@infoloom.com; =
topicmaps-comment@lists.oasis-open.org
 &gt; Subject: Re: [topicmapmail] XML Schema for XTM =
DTD
 &gt; 
 &gt; 
 &gt; DTD has more limitations than XSD.
 &gt; 
 &gt; I'd prefer to see an XSD schema as the source =
of truth, DTD 
 &gt; for those who
 &gt; are still using it and RelaxNG can also =
normative as long as 
 &gt; the target XML
 &gt; document is still valid for the XSD.
 &gt; 
 &gt; However, UDDI we will need an XSD schema of XTM =
for adoption.
 &gt; 
 &gt; Cheers,
 &gt; Max
 &gt; 
 &gt; 
 &gt; ----- Original Message -----
 &gt; From: &quot;Daniel L. Koger&quot; =
&lt;daniel@kogers.com&gt;
 &gt; To: &quot;Steve Pepper&quot; =
&lt;pepper@ontopia.net&gt;; &lt;topicmapmail@infoloom.com&gt;
 &gt; Cc: &quot;Max Voskob&quot; =
&lt;mvoskob@msi.net.nz&gt;
 &gt; Sent: Monday, February 03, 2003 7:37 AM
 &gt; Subject: RE: [topicmapmail] XML Schema for XTM =
DTD
 &gt; 
 &gt; 
 &gt; &gt; That would definitely have my support =
:)
 &gt; &gt;
 &gt; &gt; -----Original Message-----
 &gt; &gt; From: Steve Pepper [<A =
HREF=3D"mailto:pepper@ontopia.net">mailto:pepper@ontopia.net</A>]=

<BR><FONT SIZE=3D2>&gt; &gt; Sent: Sun 2/2/2003 08:22</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; To: topicmapmail@infoloom.com</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Cc: Daniel L. Koger; Max Voskob</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Subject: Re: [topicmapmail] XML Schema for =
XTM DTD</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; At 17:15 02.02.2003 +0100, Lars Marius =
Garshol wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;| It is acceptable if the DTD is =
normative, but it would </FONT>
<BR><FONT SIZE=3D2>&gt; be nice to at</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;| least have a consistent format for =
schema.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;If there is a need for an XSDL schema =
I agree it would be good if</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;everyone used the same schema. One way =
to achieve that is </FONT>
<BR><FONT SIZE=3D2>&gt; to make it</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;an informative annex to the ISO =
standard.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I think this is the way to go. Have the =
DTD be normative and publish</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; an XSD &quot;translation&quot; as an =
annex.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Steve</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Steve Pepper, Chief Executive Officer =
&lt;pepper@ontopia.net&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Convenor, ISO/IEC JTC1/SC34/WG3&nbsp; =
Editor, XTM (XML Topic Maps)</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; Ontopia AS, Waldemar Thranes gt. 98, =
N-0175 Oslo, Norway.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; <A HREF=3D"http://www.ontopia.net/" =
TARGET=3D"_blank">http://www.ontopia.net/</A> phone: +47-23233080 GSM: =
+47-90827246</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; topicmapmail mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; topicmapmail@infoloom.com</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.infoloom.com/mailman/listinfo/topicmapmail" =
TARGET=3D"_blank">http://www.infoloom.com/mailman/listinfo/topicmapmail<=
/A></FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; topicmapmail mailing list</FONT>
<BR><FONT SIZE=3D2>&gt; topicmapmail@infoloom.com</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://www.infoloom.com/mailman/listinfo/topicmapmail" =
TARGET=3D"_blank">http://www.infoloom.com/mailman/listinfo/topicmapmail<=
/A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>=

--Boundary_(ID_nLhWHP7210JoFZ2Q6ACUfw)--