Re: Why @type is not allowed in <occupation>
Antonio Rojas Castro <[email protected]> Sat, 4 Mar 2017 14:30:21 +0100
| Newsgroups | gmane.text.tei.general |
|---|---|
| Message-ID | <CAC5WTQyE4KPi0a6OUwpAOdM2xU6q8wWSiPGRqmAAKXCv5gWZ8g@mail.gmail.com> |
Thank you for your answer, Syd. I would prefer to keep the teiHeader simple and avoid taxonomies because we are dealing winth a lot of prosopographic entries. Said that, can anyone tell me more about the reasoning behind the @type attribute? I still think it would be the best approach. Many thanks. 2017-03-03 0:14 GMT+01:00 Syd Bauman <[email protected]>: > Really good question. I'm not sure I see any reason why <occupation> > should not be a member of att.typed. Could just be an oversight. That > said, I think the expectation was that encoders would use the more > structured @code attribute approach. > > <?xml version="1.0" encoding="UTF-8"?> > <TEI xmlns="http://www.tei-c.org/ns/1.0"> > <teiHeader> > <fileDesc> > <titleStmt> > <title>tiny occupation demo</title> > </titleStmt> > <publicationStmt> > <p>unpublished, except on TEI-L as a demo</p> > </publicationStmt> > <sourceDesc> > <p>born digital</p> > </sourceDesc> > </fileDesc> > <encodingDesc> > <classDecl> > <taxonomy> > <category> > <catDesc>primary</catDesc> > <category xml:id="to1.hx"><catDesc> > Historian</catDesc></category> > <category xml:id="to1.ju"><catDesc>Jurist</catDesc></category> > <category xml:id="to1.st"><catDesc>Statistician</catDesc></ > category> > <category xml:id="to1.xp"><catDesc>XML > Progammer/Analyst</catDesc></category> > <category xml:id="to1.pa"><catDesc> > Assasin</catDesc></category> > <category xml:id="to1.ct"><catDesc>Chemistry > teacher</catDesc></category> > </category> > <category> > <catDesc>secondary</catDesc> > <category xml:id="to2.hm"><catDesc>Courtmaster</catDesc></ > category> > <category xml:id="to2.dd"><catDesc>Drug > dealer</catDesc></category> > <category xml:id="to2.em"><catDesc> > Embezzler</catDesc></category> > </category> > </taxonomy> > </classDecl> > </encodingDesc> > </teiHeader> > <text> > <body> > <listPerson> > <person xml:id="WW"> > <persName>White, Walter</persName> > <occupation from="1992" to="2013" code="#to1.ct"/> > <occupation from="2008" to="2013" code="#to2.dd"/> > </person> > </listPerson> > </body> > </text> > </TEI> > > > > I am encoding a very detailed prosopography of a person that had > > many occupations with the element <occupation>. We would like to > > distinguish his “main” occupations from his “secondary” > > occupations. Here is an example: > > > > <person> > > > > <!— some elements here --> > > > > <occupation from="1785">Historiker</occupation> > > <occupation>Jurist</occupation> > > <occupation>Statistiker</occupation> > > > > <occupation>Hofmeister / Söhne des Kanzlers von Gersdorff > in > > Dresden 1743-46</occupation> > > <occupation >PD philos. / Geschichte, Statistik, Natur- > und > > Völkerrecht Marburg 1746-</occupation> > > <occupation>aoP. philos. / Geschichte u. Statistik > Göttingen > > 1748-</occupation> > > <occupation>aoP. iur. / Göttingen April 1753-</occupation> > > > > <!— more elements here --> > > > > </person> > > > > For this reason, I had a look at the content model model.personPart > > <http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref- > model.personPart.html>. > > Most of its elements accepts the attribute @role whereas only > > <persName>, <state> and <trait> accept the attribute @type. > > > > Can anyone explain why <occupation> is not permitted to contain a > > @type attribute? Or is there a better solution for my problem? > -- Antonio Rojas Castro Research assistant, Cologne Center for eHumanities Communication coordinator, EADH www.antoniorojascastro.com