LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  February 2010

TEI-L February 2010

Subject:

Re: name vs. persName class memberships

From:

Martin Holmes <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Wed, 3 Feb 2010 10:31:21 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (97 lines)

Hi Markus,

 > (2) On the other hand, why are <gi>persName</gi> and
 > <gi>placeName</gi> members of att.datable ("provides attributes for
 > normalization of elements that contain dates, times, or datable
 > events"), att.dimensions ("provides attributes for describing the size
 > of physical objects"), or att.ranging ("provides attributes for
 > describing numerical ranges")? Does anyone make any use of that? (If
 > so, how?)

In our Despatches project, the names of geographical locations are in 
flux over the period of our documents, and later. For instance, what is 
now Mount Douglas was originally called Cedar Hill; nowadays Cedar Hill 
is the name of a district which doesn't actually include Mount Doug. I 
can see a lot of value in:

<placeName xml:id="mount_douglas" notBefore="1843">Mount Douglas</placeName>

<placeName key="mount_douglas" notAfter="1843">Cedar Hill</placeName>

to both disambiguate and link together the two terms for the place. 
Similarly, we have somefirst-nations place names recorded with wildly 
variant spellings, which later are replaced by English names.

There are also lots of scenarios in which you might want to record the 
dimensions of a place (Fort Victoria, for instance -- we have plans of 
the fort from various points in its history). I can't at the moment 
think of much use for numerical ranges, though.

A <persName> might use dating attributes for similar reasons -- names 
change through marriage or inheritance of a title, or are changed for 
other reasons.

Cheers,
Martin

Markus Flatscher wrote:
> Dear list,
> 
> comparing the declarations for <gi>persName</gi> [1] and its
> syntactic-sugar friends with the old generic <gi>name</gi> [2] makes
> me wonder why the declaration of <gi>name</gi> is so much more
> restrictive.
> 
> Specifically, I wonder:
> 
> (1) Shouldn't <gi>name</gi> be a member of att.responsibility, like
> <gi>persName</gi>? I can imagine use cases for @cert on <gi>name</gi>.
> 
> (2) On the other hand, why are <gi>persName</gi> and
> <gi>placeName</gi> members of att.datable ("provides attributes for
> normalization of elements that contain dates, times, or datable
> events"), att.dimensions ("provides attributes for describing the size
> of physical objects"), or att.ranging ("provides attributes for
> describing numerical ranges")? Does anyone make any use of that? (If
> so, how?)
> 
> Thanks everyone,
> 
> M.
> 
> [1]
> element persName
> {
>    att.global.attributes,
>    att.datable.w3c.attributes,
>    att.datable.iso.attributes,
>    att.editLike.attributes,
>    att.dimensions.attributes,
>    att.ranging.attributes,
>    att.responsibility.attributes,
>    att.personal.attributes,
>    att.naming.attributes,
>    att.canonical.attributes,
>    att.typed.attributes,
>    macro.phraseSeq
> }
> 
> [2]
> element name
> {
>    att.global.attributes,
>    att.naming.attributes,
>    att.canonical.attributes,
>    att.typed.attributes,
>    macro.phraseSeq
> }
> 

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
([log in to unmask])
Half-Baked Software, Inc.
([log in to unmask])
[log in to unmask]

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager