[tei-council] mimeType=

Lou Burnard lou.burnard at computing-services.oxford.ac.uk
Wed Jun 13 03:37:59 EDT 2007


Sounds like an open and shut case to me : plz do it forthwith

Syd Bauman wrote:
> We now have 4 elements which each individually declare a mimeType=
> attribute. 
>
> <binaryObject> attribute mimeType { data.word }?, mwa
>   The MIME type to be used for the object when it is decoded
>
> <equiv>        attribute mimeType { data.word }?, opt
>   MIME type of external filter script
>
> <graphic>      attribute mimeType { data.word }?, mwa
>   The MIME type
>
> <rendition>    attribute mimeType { text }?, [defaults to opt]
>   supplies a MIME type for the content of this element.
>
>
> Recommendation
> --------------
> New class, att.internetMedia (or whatever) that defines the mimeType=
> attribute as 'mwa' with datatype data.word, and a description of
> "specifies the applicable multimedia internet mail extension (MIME)
> media type". These four elements become members of this class. The
> remarks element for this class would include a reference to the MIME
> type registry (http://www.iana.org/assignments/media-types/).
>
> This means that the information about *what* the attribute is the
> MIME type for, and (in the case of <binaryObject>) that the contents
> need to be decoded before the MIME type applies, will need to be
> noted in the remarks section of the tagdoc for the element.
>
> It's also a real change in the case of <equiv>, from optional to
> mandatory when applicable.
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
>   




More information about the tei-council mailing list