Print

Print


Hi Dot,

(Incidentally,) don't your parsers/validators complain about faulty ID 
values? (Some of your xml:id are URI strings.)

Best regards,

   Piotr

On 16/11/15 16:40, Dot Porter wrote:
> Thanks for answering my query, Kevin, but what I want to do isn't
> actually that simple. The context is a model I'm working up for physical
> collation, where I want to apply terms to specific leaves, not to an
> entire document. Here's a longer example, showing three taxonomies - one
> my project taxonomy (Canterbury Tale texts and booklet markers), one
> from AAT (physical descriptors) and one a book by Michelle Brown:
>
> <taxonomyxml:id="b"xmlns="http://www.tei-c.org/ns/1.0">
> <bibl>Our project typology</bibl>
> <categoryxml:id="b.a">
> <catDesc>Textual</catDesc>
> <categoryxml:id="b.a1">
> <catDesc>General Prologue</catDesc>
> </category>
> <categoryxml:id="b.a2">
> <catDesc>Miller's Tale</catDesc>
> </category>
> <categoryxml:id="b.a3">
> <catDesc>Knight's Tale</catDesc>
> </category>
> <categoryxml:id="b.a4">
> <catDesc>Reeve's Tale</catDesc>
> </category>
> <categoryxml:id="b.a5">
> <catDesc>Cook's Tale</catDesc>
> </category>
> <categoryxml:id="b.a6">
> <catDesc>Wife of Bath's Tale</catDesc>
> </category>
> </category>
> <categoryxml:id="b.d">
> <catDesc>Booklets</catDesc>
> <categoryxml:id="b.d1">
> <catDesc>Booklet 1</catDesc>
> </category>
> <categoryxml:id="b.d2">
> <catDesc>Booklet 2</catDesc>
> </category>
> </category>
> </taxonomy>
> <!-- I want to point to the main AAT and to the individual definitions -->
> <taxonomyxml:id="c"xmlns="http://www.tei-c.org/ns/1.0">
> <bibl>Getty Art and Architecture Thesaurus</bibl>
> <categoryxml:id="c.300011851">
> <catDesc>Parchment</catDesc>
> </category>
> <categoryxml:id="c.300014179">
> <catDesc>Paper</catDesc>
> </category>
> </taxonomy>
> <taxonomyxml:id="d"xmlns="http://www.tei-c.org/ns/1.0">
> <bibl>Michelle P. Brown, Understanding Illuminated Manuscripts: A Guide
> to Technical Terms (J.
>        Paul Getty Museum: Malibu and British Library: London, 1994),
> online on the British Library
>        website</bibl>
> <categoryxml:id="https://www.bl.uk/catalogues/illuminatedmanuscripts/GlossH.asp#hairside">
> <catDesc>Hair side</catDesc>
> </category>
> <categoryxml:id="https://www.bl.uk/catalogues/illuminatedmanuscripts/GlossF.asp#fleshside">
> <catDesc>Flesh side</catDesc>
> </category>
> </taxonomy>
>
> In a separate section of the document I'm listing all the leaves by
> quire, and I want to link those leaves to the terms that define them in
> yet another mapping section, which will probably look something like
> this (note that these @refs don't correspond to the list above, because
> I'm still messing around at this point - but this is how I'd like it to
> work):
>
> <mappingxmlns="http://schoenberginstitute.org/schema/mapping">
> <mapleaf="1.2"side="r">
> <typologyref="#tl1">
> <typeref="#tl1-1"/>
> </typology>
> <typologyref="#tl2">
> <typeref="#tl2-1"/>
> </typology>
> </map>
> <mapleaf="1.2"side="v">
> <typologyref="#tl1">
> <typeref="#tl1-1"/>
> <typeref="#tl1-2"/>
> </typology>
> </map>
> </mapping>
>
> I hadn't considered using tei:keyword at all, because as you note that
> section is set up to apply keywords to an entire document, which isn't
> what I'm doing.
>
> I'm probably going to have to go outside of the TEI for this, if it's
> really not what tei:taxonomy was built for, but I wanted to see if I
> could make it work first.
>
> Thanks,
>
> Dot
>
>
> On Sat, Nov 7, 2015 at 10:16 AM, Kevin Hawkins
> <[log in to unmask]
> <mailto:[log in to unmask]>> wrote:
>
>     I'm a bit confused.  If I understand correctly:
>
>     a) You want to use both some local, project-specific taxonomies and
>     some standard, externally defined taxonomies.
>
>     b) You want to define both using <tei:taxonomy>.
>
>     c) Your example shows the definition for just a single externally
>     defined taxonomy (the Getty Art and Architecture Thesaurus).
>
>     d) Your example shows just those terms from Getty that you've used
>     in this document.
>
>     Assuming this is all correct, then I have the following comment.
>
>     I read P5 section 2.3.7 to say that you should only use <category>
>     elements if a classification scheme that is not well-recognized,
>     documented, and public.  So, for the case of Getty, I would have
>     simply done this:
>
>     <taxonomy xml:id="Getty">
>       <bibl>
>         <title>Getty Art and Architecture Thesaurus</title>
>         <edition>[whatever version number you're using]</edition>
>       </bibl>
>     </taxonomy>
>
>     and then inside profileDesc/textClass, you'd include the terms from
>     Getty that relate to your document:
>
>     <keywords scheme="#Getty">
>        <term ref="[URL for this term on the Getty website]">Parchment</term>
>        <term ref="[URL for this term on the Getty website]">Paper</term>
>        <term ref="[URL for this term on the Getty website]">Insular
>     majuscule</term>
>        <term ref="[URL for this term on the Getty website]">Insular
>     minuscule</term>
>     </keywords>
>
>     In short, it's important to remember that the TEI header separates
>     the declaration of classification schemes (in <classDecl>) and the
>     application of these schemes to a particular document (in profileDesc).
>
>     Kevin
>
>
>     On 11/6/15 2:47 PM, Dot Porter wrote:
>
>         Hi everyone,
>
>         I'm experimenting with using tei:taxonomy to create a set of
>         taxonomies
>         both project-specific (invented by me) and pulling from external
>         sources
>         (e.g., Getty Art and Architecture Thesaurus). I'm stymied
>         because there
>         doesn't seem to be a native way to point from terms
>         (tei:category) to a
>         uri defining an eternally defined term. So I'm doing this:
>
>         <taxonomyxml:id="c"xmlns="http://www.tei-c.org/ns/1.0">
>         <bibl>Getty Art and Architecture Thesaurus</bibl>
>         <category>
>         <catDesc>Physical descriptors</catDesc>
>         <categoryxml:id="c.300011851">
>         <catDesc>Parchment</catDesc>
>         </category>
>         <categoryxml:id="c.300014179">
>         <catDesc>Paper</catDesc>
>         </category>
>         </category>
>         <category>
>         <catDesc>Scripts</catDesc>
>         <categoryxml:id="c.300210143">
>         <catDesc>Insular majuscule</catDesc>
>         </category>
>         <categoryxml:id="c.300210146">
>         <catDesc>Insular minuscule</catDesc>
>         </category>
>         </category>
>         </taxonomy>
>
>         Where the long number in the tei:category/xml:id is the ID
>         number of the
>         term within the AAT, and I can use that to construct a URI during
>         processing. But I'd rather have a pointer for the URI (really a
>         URL to
>         the definition on the AAT website) directly in the encoding.
>
>         Is this possible, and I've just overlooked it? Or is there
>         another way
>         to do this in TEI that's not tei:taxonomy? Is this a potential
>         feature
>         request?
>
>         Thanks,
>
>         Dot
>
>
>         --
>         *~*~*~*~*~*~*~*~*~*~*
>         Dot Porter (MA, MSLS)
>         Digital Medievalist, Digital Librarian
>         Email: [log in to unmask] <mailto:[log in to unmask]>
>         <mailto:[log in to unmask] <mailto:[log in to unmask]>>
>         Personal blog: dotporterdigital.org
>         <http://dotporterdigital.org> <http://dotporterdigital.org>
>         Medieval Electronic Scholarly Alliance: http://www.mesa-medieval.org
>         MESA blog: http://mesamedieval.wordpress.com/
>         MESA on Facebook:
>         https://www.facebook.com/MedievalElectronicScholarlyAlliance
>         *~*~*~*~*~*~*~*~*~*~*
>
>
>
>
> --
> *~*~*~*~*~*~*~*~*~*~*
> Dot Porter (MA, MSLS)
> Digital Medievalist, Digital Librarian
> Email: [log in to unmask] <mailto:[log in to unmask]>
> Personal blog: dotporterdigital.org <http://dotporterdigital.org>
> Medieval Electronic Scholarly Alliance: http://www.mesa-medieval.org
> MESA blog: http://mesamedieval.wordpress.com/
> MESA on Facebook:
> https://www.facebook.com/MedievalElectronicScholarlyAlliance
> *~*~*~*~*~*~*~*~*~*~*