[tei-council] [Fwd: Re: Proposal <idno> coverage -SF 2493417]

[Peter Boot]

Peter Boot schreef:
> 1. Mixed content
> -- ----- -------
> I concur wholeheartedly with Lou's aversion to
>      <author>
>         <idno type="nldai">info:eu-repo/dai/nl/12456454</idno>
>         <idno type="openid">https://me.yahoo.com/johndoe61</idno>
>         John Doe
>      </author>
> How do you access the name?  (...)

OK, this seems to be a general sentiment then.

> 2. author identification number
> -- ------ -------------- ------
> On the original issue Peter raised, some thoughts jump to mind.
> 
> * Who says that key= can't have multiple values? Certainly it can,
>    syntactically, since the syntax is entirely up to the user. The
>    only thing that seems to stop one from using it this way is that
>    the Guidelines refer to its value in the singular ("a coded value
>    by means of an arbitrary identifier").

Using multiple values would lead to something like:
    key="nldai:info:eu-repo/dai/nl/12456454
         openid:https://me.yahoo.com/johndoe61"

> * We have gone to great lengths to develop a lovely mechanism for
>    encoding details about a person (or organization): 
>    (...)
>    are the use-cases here so different as to render our current
>    mechanism -- which would be to point to a <person> or <org> from
>    the ref= of either <author> itself or of the <persName> or
>    <orgName> child of the <author>, and then use <state> or <idno>
>    (currently not allowed) in the <person> or <org> -- insufficient?)

I agree this is a possible approach, but it seems like using a 
sledgehammer to crack a nut.

> 3. encoding of author
> -- -------- -- ------
> (...)
> My logic is that I don't want the computer to have to read the
> content of <author> to figure out how many people or organizations
> are involved. I point out that with
>       <author>Peter Boot and Kevin Hawkins</author>
> the simple computer program has no way to know there are two authors.

Which is why I would use multiple author elements. If we were do what I 
advocate, i.e. use <idno> within <author> as implictly applying to that 
author, the understanding would have to be that this <author> element 
refers to a single author.

> (Would have to parse out the "and" and to know that you didn't use "&amp;"
> or "y", which means it's no longer simple.) But
>            <author>
>              <persName>
>                <surname>Boot</surname>
>                <forename>Peter</forename>
>              </persName>
>              <persName>
>                <surname>Hawkins</surname>
>                <forename>Kevin</forename>
>              </persName>
>            </author>
> is pretty darn clear. (I personally don't generally bother with the
> sub-<persName> components, though.)
> 
> Thus I think that <author> should say "I contain an indication of the
> entity or entities that bear primary responsibility for the item
> being described" without confounding that statement by also trying to
> indicate that the method of indication is a name.
> 
> Notes
> -----
> [1] And if you know it's the last thing, you could use
>         author/text()[ count(../child::*)+1 ]
>      but that doesn't feel more stable at all.
> 
> 
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
>