[tei-council] multiple representations of a graphic/media

[Fabio Ciotti]

I agree with Lou, don't like the nesting solution for semantic
reasons, even if it can be bounded to a good processing model. Nesting
in general means that something is part of something else (in various
ways) and this is not the case, since we have a parallelism of
sources.

A TEI as-is compatible solution could be to insert <media> inside
<figure>, so that you can put in sequence as many <media> elements as
many formats you have. This of copurse soounds odd for video and
especially for audio again for semantic reason, but the power of
metaphor can give an help here. Otherwise I'd suggest to give a
structure to <media> similar to that of <figure>, or better of METS
<fileGrp>

My 2 cents

Fabio

2014-04-28 19:08 GMT+02:00 Lou Burnard <lou.burnard at retired.ox.ac.uk>:
> On 28/04/14 17:22, Martin Holmes wrote:
>>
>>> Secondly, if they could, what would it mean? Surely, it would mean that
>>> the media was composed of several other media. Which is not the same at
>>> all as these several other media are alternatives for each other, which
>>> is the use case here as farv as I understand it.
>> The idea is based on what HTML does with <object>, which works very well:
>>
>> <http://www.w3.org/TR/REC-html40/struct/objects.html#h-13.3>
>>
>> The user-agent is expected to use the first one in the tree that it's
>> able to handle. At the bottom level is a text fallback that can be
>> displayed when nothing else works; we already have <desc> for that.
>>
>
> This is fine for HTML, which is a language intended to tell you how to
> process a document, but is not necessarily a good model for TEI, which
> is a language intended to tell you how a document is organized. If you
> want <html:object>, use that.
>
>
>
> --
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
> PLEASE NOTE: postings to this list are publicly archived