Registration of media type application/xtm+xml
I intend to submit the following media type registration to the IESG for registration with IANA. However, before then I would welcome community review and feedback on the proposed registration. If you see any problems, please let me know. Assuming that the appropriate form for such a media type registration would be an RFC-style document I wrote one up using the xml2rfc syntax and published it here: http://www.isotopicmaps.org/sam/xtm-rfc.html The actual registration part is included below. --------------------------------------------------------------------- This is a media type registration as defined in RFC 4288, "Media Type Specifications and Registration Procedures" [RFC4288]. *MIME media type name:* application *MIME subtype name:* xtm+xml *Required parameters:* none *Optional parameters:* charset Same as charset parameter of application/xml, defined in RFC 3023 [RFC3023]. *Encoding considerations:* Same as encoding considerations of application/xml, defined in RFC 3023 [RFC3023]. *Security considerations:* See Section 5. *Interoperability considerations:* _NEED TO WRITE THIS PART_ *Published specification:* See the Topic Maps Data Model [ISO13250-2] and the XTM specification [ISO13250-3]. *Applications which use this media type:* XTM is device-, platform-, and vendor-neutral and is supported by a range of applications and web services. *Magic number(s):* none Although no byte sequences can be counted on to consistently identify XTM, XTM documents will have the sequence "http://www.topicmaps.org/xtm/" to identify the XTM namespace. This will usually be near the top of the document. *File extensions(s):* .xtm *Macintosh File Type Code(s):* "xtm " *For further information:* contact the editors, Lars Marius Garshol <larsga@garshol.priv.no> and Graham Moore <graham.moore@networkedplanet.com>, or ISO SC34. More information may be found on the website of ISO SC34 WG3: <http://www.isotopicmaps.org>. *Intended usage:* COMMON *Author/Change controller:* The XTM standard was produced by ISO SC34, which has change control over the standard. --------------------------------------------------------------------- --Lars M. http://www.garshol.priv.no/tmphoto/ http://www.garshol.priv.no/blog/
* Lars Marius Garshol
*Interoperability considerations:* _NEED TO WRITE THIS PART_
I omitted this part by mistake. My apologies. Here is the correct text: *Interoperability considerations:* It is RECOMMENDED that XTM documents use the new XTM 2.0 syntax [ISO13250-3] as opposed to the older XTM 1.0 syntax [XTM1.0]. In general use of features of XML which XML processors may choose not to support should be avoided. --Lars M. http://www.garshol.priv.no/tmphoto/ http://www.garshol.priv.no/blog/
* Lars Marius Garshol wrote:
Assuming that the appropriate form for such a media type registration would be an RFC-style document I wrote one up using the xml2rfc syntax and published it here:
An RFC would be the proper form; an alternative would have been for ISO to include the registration information in the relevant ISO standard. Note that you have to publish the document as Internet-Draft before the IESG will consider it for publication as RFC.
*Applications which use this media type:* XTM is device-, platform-, and vendor-neutral and is supported by a range of applications and web services.
This should rather describe the general categories of applications, like, say, computer aided drawing programs, web browsers, and so on.
*For further information:* contact the editors, Lars Marius Garshol <larsga@garshol.priv.no> and Graham Moore <graham.moore@networkedplanet.com>, or ISO SC34. More information may be found on the website of ISO SC34 WG3: <http://www.isotopicmaps.org>.
Following the template in RFC 4288 this should be "Person & email address to contact for further information".
*Author/Change controller:* The XTM standard was produced by ISO SC34, which has change control over the standard.
This should probably be "The IESG." as it concerns the definition of the media type, not the underlying data format. If ISO wishes to get change control over the type, they are welcome to talk to the IESG. Similarily, the authors would be the authors of the registration. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
* Bjoern Hoehrmann
An RFC would be the proper form; an alternative would have been for ISO to include the registration information in the relevant ISO standard.
We could put the information in the ISO standard, but realistically that would take years because of the voting requirements, so I think an RFC is the best route for this.
Note that you have to publish the document as Internet-Draft before the IESG will consider it for publication as RFC.
Okay. I'll figure out how to do that and do it once the registration part passes review here.
[Applications which use this media type]
This should rather describe the general categories of applications, like, say, computer aided drawing programs, web browsers, and so on.
Oh dear. That's not easy, since this is a generic format. A lot of the tools which implement it are generic Topic Maps frameworks used to build other tools. Applications based on these have been deployed in everything from web portals, product configuration tools, and e-learning systems to intelligence and police systems. So I could say "web portals", which is a common use, but it's kind of misleading, because really the *media type* is going to be used by web service interfaces of all kinds. Would something like the below work? XTM is a generic data format, and as such is used by a wide range of applications. So far, common applications have been web portals, content management, and e-learning. You can see an incomplete list of tools here, but I doubt it helps: http://www.garshol.priv.no/tmtools/technology.jsp?id=xtm-10 RDF/XML has similar problems, and simply wrote: RDF is device-, platform-, and vendor-neutral and is supported by a range of Web user agents and authoring tools. which is very similar to what I wrote. Some web user agents, like clients of Topic Maps-based web services do use XTM. So maybe I should add that?
Following the template in RFC 4288 this should be "Person & email address to contact for further information".
Ok. Changed.
This should probably be "The IESG." as it concerns the definition of the media type, not the underlying data format. If ISO wishes to get change control over the type, they are welcome to talk to the IESG. Similarily, the authors would be the authors of the registration.
Ok. Also changed. --Lars M. http://www.garshol.priv.no/tmphoto/ http://www.garshol.priv.no/blog/
Why not be more precise such as "any tool that can process or produce topics and relationships among them about any possible entity; this has included, in the past, ... and your list...". I would agree you have no reason to be more precise than RDF but indeed, their statement is bloated. Maybe it would be possible from this paragraph to deduce that you have similar ambitions to RDF? paul Le 19-nov.-09 à 18:59, Lars Marius Garshol a écrit :
[Applications which use this media type]
This should rather describe the general categories of applications, like, say, computer aided drawing programs, web browsers, and so on.
Oh dear. That's not easy, since this is a generic format. A lot of the tools which implement it are generic Topic Maps frameworks used to build other tools. Applications based on these have been deployed in everything from web portals, product configuration tools, and e- learning systems to intelligence and police systems.
So I could say "web portals", which is a common use, but it's kind of misleading, because really the *media type* is going to be used by web service interfaces of all kinds.
Would something like the below work?
XTM is a generic data format, and as such is used by a wide range of applications. So far, common applications have been web portals, content management, and e-learning.
You can see an incomplete list of tools here, but I doubt it helps: http://www.garshol.priv.no/tmtools/technology.jsp?id=xtm-10
RDF/XML has similar problems, and simply wrote:
RDF is device-, platform-, and vendor-neutral and is supported by a range of Web user agents and authoring tools.
which is very similar to what I wrote. Some web user agents, like clients of Topic Maps-based web services do use XTM. So maybe I should add that?
* Paul Libbrecht
Why not be more precise such as "any tool that can process or produce topics and relationships among them about any possible entity; this has included, in the past, ... and your list...".
Hmmmm. Well. Unfortunately, this isn't entirely true, as it takes a bit more than that to support Topic Maps. But I could turn it around and make it something like this: Applications which use this media type: Any tool which can process or produce data according to the Topic Maps Data Model. This has included in the past generic Topic Maps tools, web portals, product configuration tools, e-learning systems, and a variety of web services and web service clients. Would this work?
I would agree you have no reason to be more precise than RDF but indeed, their statement is bloated.
It's pretty vague, yes.
Maybe it would be possible from this paragraph to deduce that you have similar ambitions to RDF?
I hope it would, but it's kind of hard for me as an insider to judge. --Lars M. http://www.garshol.priv.no/tmphoto/ http://www.garshol.priv.no/blog/
On 2009/11/20 18:19, Lars Marius Garshol wrote:
* Paul Libbrecht
Why not be more precise such as "any tool that can process or produce topics and relationships among them about any possible entity; this has included, in the past, ... and your list...".
Hmmmm. Well. Unfortunately, this isn't entirely true, as it takes a bit more than that to support Topic Maps. But I could turn it around and make it something like this:
Applications which use this media type: Any tool which can process or produce data according to the Topic Maps Data Model. This has included in the past generic Topic Maps tools, web portals, product configuration tools, e-learning systems, and a variety of web services and web service clients.
This looks very good. Not too specific, not too general. Regards, Martin. -- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp
* Martin J. Dürst
This looks very good. Not too specific, not too general.
Excellent. Thank you all! I have updated the proposed internet draft at http://www.isotopicmaps.org/sam/xtm-rfc.html If nobody has any more comments I'll go ahead and try to get this published as a real Internet-Draft. --Lars M. http://www.garshol.priv.no/tmphoto/ http://www.garshol.priv.no/blog/
participants (4)
-
"Martin J. Dürst" -
Bjoern Hoehrmann -
Lars Marius Garshol -
Paul Libbrecht