#326 an <object> element

Sebastian Rahtz

From the meeting of the TEI Ontology SIG at the members meeting 2011-10-14.

Just as we now have <place>, <person>, <event> and <org>, we suggest that the TEI needs an <object> element with the
same semantics, content model and placement (mutatis mutandis) as <place> or <person> (this means a corresponding <listObject> in
model.biblLike). It would be used to create authority lists of identifiable physical objects (eg Excalibur, a statue of Augustust, a copy of the first folio,
a dress worn by Queen Elizabeth, a mouse trap). One might regard it as a general purpose replacement for <msDesc>. It is NOT a place to record classes of objects ("sword", "art work" etc).


  • Lou Burnard
    Lou Burnard

    • milestone: --> AMBER
  • Lou Burnard
    Lou Burnard

    We're really straying into museum country here, of course. But why not.

  • Peter Stadler
    Peter Stadler

    I second this request. It's not about museums but physical objects in a text!

  • Kevin Hawkins
    Kevin Hawkins

    Council agrees to this proposal and asks the SIG to draft revisions to the Guidelines (similar to a briefer version of http://www.tei-c.org/Activities/Council/Working/tcw21.html ) with examples and summary of content models for the following:

    a) create <listObject> in model.biblLike, which contains <object> elements (cf. <listPlace> and <place>), and add prose Guidelines about use of this for physical objects, not classes of objects.

    b) create <objectName> (cf. <placeName>), and add prose Guidelines about use of this for referrents to physical objects, not classes of objects.

    Council will consider the formal proposal.

  • James Cummings
    James Cummings

    Council should remind the SIG that we are waiting for a proposal.

  • Elli Mylonas
    Elli Mylonas

    Sebastian/Torsten to prod SIG for proposal.