Skip to content

Missing documentation: <physMedium> #29

@gucl-mu

Description

@gucl-mu

I quickly created a new issue so that we don't get confused and the discussion runs separately. This is @riedde s first draft:

Within physMedium the material of which an object is composed (physical materials, such as ink, paper, etc.) can be recorded. This can be done by using a single physMedium element containing the whole description or by using multiple physMedium elements for recording different materials separately. This container element may contain textual content and semantic markup. Because of the rich model class model.physDescPart the container can also contain highly structured code.

<physDesc xmlns="http://www.music-encoding.org/ns/mei" meiversion="5.1-dev+anyStart"> <physMedium>Thick yellow paper.</physMedium> <physMedium>Extra paper <height unit="mm">35</height>x<width unit="mm">150</width> glued on the source.</physMedium> <physMedium>Black ink is used for the notes, red ink for the dynamics</physMedium> </physDesc>

by using multiple physMedium elements for recording different materials separately. --> I would not recommend this, on the one hand I wonder whether a source can have more than one physMedium. Is it one object carrier or several (more of a philosophical question perhaps). More importantly, it seems to me that the same effect you suggest can be achieved within a physmedium through paragraphs. On the other hand, physMedium as an element with its history (no equivalent in TEI and introduced because the object description was not as mature earlier in MEI 3) is a remnant and perhaps one should rather suggest using the numerous other elements such as <supportDesc>, <extent>, <dimensions> etc. For me it would be important to clarify how physMedium relates to other elements such as <supportDesc>, <handList> or <bindingDesc>. And then whether these elements might be linked to each other

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

New

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions