Dear Piotr,

to be honest I would suggest you to adopt other metadata schema much
more apt at this, like MODS, or if you want to concentrate on tech and
prov metadata PREMIS, or else if you want all this and more METS. That
said during last tech council meeting we have worked on a proposal for
adding a container element to include metadata from outer schema/
namespace inside the TEI Header and that could be a potential solution
for your use case.

Iff you really want to use TEI and only TEI, at the moment I do not
see any elegant solution, but only tricks. The ontology of metadata
section in TEI is a bit outdated imho, something to work on for P6!

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
where <mods:extent> is.

ANother solution is the usage of <noteStmt> and <note> with a @type
attribute, where yuo can express the mime type:

<note type="mimetype">application/pdf</note>

You can control the correct usage of the note with Schematron.


2015-02-18 22:20 GMT+01:00 Piotr BaƄski <[log in to unmask]>:
> Hello everyone,
> I would like to be able to express, within the fileDesc, the same
> information as <dc:format>application/pdf</dc:format> expresses.
> When you prepare a header for an electronic version of a book that is not
> XML-encoded (in my case it's PDF -- the header will be free-standing), and
> you would like to specify the media type of the book file, how do you go
> about that, please?
> Should I just use a <ref> or a <ptr> somewhere within the publicationStmt
> (or notesStmt?), so that I can sneak @mimeType into it? But if I do, it is
> going to be different from a direct statement that I would like to express
> in a machine-readable form -- hence, among others, in a well-defined
> position in the header. Am I missing something obvious, please?
> One hack I've been thinking of is to use <media> under (or next to)
> <measure> under <extent>.
> So, for example:
> <extent>
>   <measure unit="MiB" quantity="1.4"/>
>   <media url="my_book.pdf" mimeType="application/pdf"/>
> </extent>
> But this solution has a kludgy tinge to it. And I think it places the rather
> first-order information about the location of the file and about it's media
> type in an almost accidental place in the header.
> Thanks in advance for any hints you care to offer.
> Best,
>   Piotr