Lou and Sigfried --
Thanks.
One little piece that can be added to what Siegfried says is PR-related,
along the lines "Docbook has it, TEI does not -- and why shouldn't it?".
James and I are trying to make Sourceforge notice TEI as a separate data
format [1] (no reaction so far, perhaps someone might wish to add their
voice to our sweet sopranos?) -- and IANA is obviously a much heavier
calibre. And far greater range.
Naturally, what Sourceforge might want to reply is that TEI is XML all
the way down, but that can be said of many of the other data formats
listed there. This is of course a toy case compared to IANA
registration, but if Siegfried's trail of reasoning is followed, I think
a case might be built for application/tei+xml (text/ is troublesome, as
Siegfried's links suggest).
Best,
Piotr
[1]
http://sourceforge.net/tracker/index.php?func=detail&aid=2897522&group_id=1&atid=350001
more at http://wiki.tei-c.org/index.php/Sourceforge_topic_categories
Sigfrid Lundberg writes:
> The docbook mime type is documented in an internet draft
>
> http://tools.ietf.org/html/draft-walsh-app-docbook-xml-00
>
> it expired a year or so ago. Don't know why it wasn't renewed.
> Perhaps the work with XProc and Calabash too much time.
>
> In general, an XML application is a document format defined using XML
> as opposed to applications that are processing XML documents which
> are xml processors. In my view TEI is an XML application. Mime types
> for XML applications are described in RFC3023
> (http://tools.ietf.org/html/rfc3023), which clearly states that mime
> types like
>
> application/mathml+xml
>
> is the preferred form. There are also a discussion of this in the
> recommendation from the W3C "Architecture of the World Wide Web"
> (http://www.w3.org/TR/webarch/#xml-media-types)
>
> These practices are now very much integrated in the REST design
> patterns for web applications. I'd like to take a few examples:
>
> One could imagine that someone would like to publish TEI documents
> using the atom publishing protocol. That is explicitely prohibited
> for other text/* mime types except text/html. XML documents published
> using this protocol must be application/*+xml.
>
> Consider the situation that we have the same content available
> through a REST web service, where the representation is chosen
> through the accept http header, then what if there are more than one
> XML representation, should TEI then use text/xml and docbook
> application/docbook+xml? Well, one could live with that, but
> harvesters that where not prepared for this in advance couldn't.
>
> The TEI community is really good at XML, but a registered
> applicaiton/tei+xml would demonstrate to the world that we regard
> ourselves as a part of the Wordwide web as well.
>
> Yours
>
> Sigfrid
>
>
>
>
>
> ________________________________________ Fra: TEI (Text Encoding
> Initiative) public discussion list [[log in to unmask]] På
> vegne af Lou Burnard [[log in to unmask]] Sendt: 21. november
> 2009 18:34 Til: [log in to unmask] Emne: Re: TEI MIME type
>
> Council discussed this recently, and reached the conclusion that
> there was no advantage (or indeed much sense) in registering a
> TEI-specific MIME type. It's XML all the way down; not an application
> as such.
>
> Piotr Bański wrote:
>> Is there one?
>>
>> Docbook claims to have "application/docbook+xml", but I can't find
>> it at IANA:
>>
>> http://www.iana.org/assignments/media-types/application/
>>
>> So I'm not sure whether the absence of application/tei+xml or
>> text/tei+xml or whatever ("tei-p5+xml"?) at IANA means that the
>> TEI's type is not registered or maybe merely not listed there.
>>
>> Thanks,
>>
>> Piotr
>
|