Subject | From | Date | Time |
Your idea of using <media> inside <extent> could work, and is vaguely
consistent with other metadata structure: for instance the mime type
in MODS goes inside the <mods:physicalDescription> area, the same
ANother solution is the usage of <noteStmt> and <note> with a @type
attribute, where yuo can express the mime type: |
(a) detection of mime type based on file extension (firefox gets this
right, IE doesn't appear to even try) |
>
> I've already had this idea (adding a mime type attribute to
> <prefixDef>) in the back of my mind for a while. This could be
>
> A processor could then choose which mime type it wants to make a link
> to, so (for instance) a processor that is creating HTML output from |
I've already had this idea (adding a mime type attribute to <prefixDef>)
in the back of my mind for a while. This could be achieved by adding
A processor could then choose which mime type it wants to make a link
to, so (for instance) a processor that is creating HTML output from the |
| Just some food for thought... I've been carrying around these problems for years, and it was this triggered my interest in a mime type for TEI to begin with. In my view it is immensely valuable to have standards for delivering data in this way. As a matter of fact it is a key to interchange of text. |
On 21/10/10 03:37, Martin Holmes wrote:
> Congratulations on progress with the mime type. I've just started
> experimenting again with this, to see what the effect would be on my |
> On 21/10/10 03:37, Martin Holmes wrote:
>> Congratulations on progress with the mime type. I've just started
>> experimenting again with this, to see what the effect would be on my |
| Now comes the point as to where I need some help: The IESG want to know what mime type we're using, and it seems that it would help our cause if this MIME type is already in use in applications. If you do, could please report back to me. |
Congratulations on progress with the mime type. I've just started
experimenting again with this, to see what the effect would be on my
When I use the application/tei+xml mime type, the browser initially
doesn't know what to do:
This makes the application/tei+xml mime type less practical than I was
hoping for Firefox, because instead of being able to view the file
I'm willing to live with the need to configure my browsers to handle the
mime type in the interests of promoting its use, but I wonder if this
will be counter-productive for regular users of my sites, who can
>
> Now comes the point as to where I need some help: The IESG want to know what mime type we're using, and it seems that it would help our cause if this MIME type is already in use in applications. If you do, could please report back to me.
> |
| I agree with Brett that everything would be easier if we could restrict ourselves to P5. I have tried to brush this difficulty under the carpet ignoring the complexity. I find it hard to believe that the first implementor of the groundbreaking REST based internet text retrieval protocol would choose TEI p4 as a starting point. On the other hand people may nevertheless want to deliver tei p4 using HTTP or send it by e-mail with a tei mime type. |
> We have come one step closer towards the registration of a tei mime type :-)
> |
| We have come one step closer towards the registration of a tei mime type :-) |
Sigfrid Lundberg writes:
> The docbook mime type is documented in an internet draft
> |
| The docbook mime type is documented in an internet draft |
>
> There has been a thread before on the issue of a TEI mime type
> |
| There has been a thread before on the issue of a TEI mime type |
From: Marcello Perathoner <[log in to unmask]>
Subject: Re: TEI mime type?
Comments: To: Sebastian Rahtz <[log in to unmask]> |
From: Marcello Perathoner <[log in to unmask]>
Subject: Re: TEI mime type?
Comments: To: Sebastian Rahtz <[log in to unmask]>
>> It is more aestetically
>> pleasing to serve them with the right mime type instead of the generic
>> text/plain. |
From: Marcello Perathoner <[log in to unmask]>
Subject: Re: TEI mime type?
In-Reply-To: <[log in to unmask]>
TEI masters along with some of our texts. It is more aestetically
pleasing to serve them with the right mime type instead of the generic
text/plain. |
From: Sebastian Rahtz <[log in to unmask]>
Subject: Re: TEI mime type?
Comments: To: Marcello Perathoner <[log in to unmask]> |
From: Sebastian Rahtz <[log in to unmask]>
Subject: Re: TEI mime type?
Comments: To: Marcello Perathoner <[log in to unmask]>
> It is more aestetically
> pleasing to serve them with the right mime type instead of the generic
> text/plain. |
From: Marcello Perathoner <[log in to unmask]>
Subject: TEI mime type?
MIME-Version: 1.0 |
From: Syd Bauman <[log in to unmask]>
Subject: Re: TEI mime type?
In-Reply-To: <[log in to unmask]> |
