Hi Alison,

(Sorry for the late reply!)

That certainly seems like a good idea. I was thinking that it seems useful to have the location, or 
co-ordinates, within with EAD - something whereby you could create visualisations based on the 
content within the EAD descriptions.

Mark's example, with Terry's modification, was:

<geogname rules="ncarules">Bristol
<extptr linktype="simple" actuate="actuatenone" show="shownone" xlink:role="OSGBGridRef"
href="http://data.ordnancesurvey.co.uk/id/100mgridsquare/ST590730"/>
</geogname>

I'm thinking that whilst this is a URI, it also includes the identifier for Bristol (ST590730), so 
that you could use this information visually. Maybe you could do the same with the IDs within your 
exmaple? (FID:875378). I'm a bit unsure - I'm not a programmer :0)

I suppose I'm thinking that there are two uses of the data (i) for a user to go and find out more 
and (ii) for us to create nice visualisations based on geographic data. Does that make sense?

cheers,
Jane.





Alison Hinderliter wrote:
> This is a potential feature we've been thinking about for our finding aids as well.
> 
> 
> - The USGS / GNIS (U.S. Geologogical Survey / Geographic Names Information System) website
> http://geonames.usgs.gov/pls/gnispublicoffers a search function for place names and contains a
> unique i.d. number, longitude and latitude coordinates, and a link to an individual feature
> report.  That report then provides links to a variety of mapping sources, including GNIS in
> GoogleMaps, USGS National Map Viewer, MapQuest, Expedia, and Yahoo Local maps.  If the URIs used
> by the GNIS are stable, I'm thinking they could become external pointers within the tag that
> leads to the USGS report, which then leads them to choose a tool to map that location. <geogname
> rules="lcsh"> Chatham (N.J.) <extptr linktype="simple" actuate="actuatenone" show="shownone" 
> href="http://geonames.usgs.gov/pls/gnispublic/f?p=gnispq:3:::NO::P3_FID:875378”> </geogname>
> 
> I haven't tried this out yet, but do you think it would work?
> 
> -Alison Hinderliter
> 
> 
> - ************************************************ Alison Hinderliter -
> [log in to unmask] Manuscripts and Archives Librarian The Newberry Library 60 W. Walton
> St. Chicago, IL  60610-7324 (312) 255-3694 FAX (312) 255-3646
> 
> Thank you for your interest in the Newberry Library! Help us continue to build and preserve our
> books, manuscripts and map collections. Learn more about donating to the Newberry at
> http://www.newberry.org/giving/donate.html
> 
>> -----Original Message----- From: Jane Stevenson <[log in to unmask]> To:
>> [log in to unmask] Date: 05/13/10 08:20 Subject: Re: Geographic names and grid references
>> 
>> Hi all,
>> 
>> Thanks for the discussion. We're keen that we can do something that covers OS grid references
>> and latitude/longitude co-ordinates. Also, I'm a little concerned that this sort of markup will
>> be rather challenging for our contributors to work with.
>> 
>> We will look at doing something in the interim, but I'm hoping that the EAD review will
>> consider enabling this kind of information to be added more easily and in a way that means
>> consistency of markup, to ensure interoperabilty with other sytems.
>> 
>> cheers, Jane.
>> 
>> 
>> Terry Catapano wrote:
>>> One minor correction to Mark's very interesting and useful extptr example. The value of the
>>> extptr's linktype or (xlink:type, in the W3C and RelaxNG versions of EAD) is fixed to
>>> "simple", so "locator" would throw a validation error. However, I believe things would be
>>> fine if the type were "simple" rather than "locator".
>>> 
>>> Also, to offer an extension to what Mark proposed, if one wanted to make clear what the thing
>>> pointed to in the exptr href is, the role/xlink:role attribute could be used. Ideally this
>>> would be a URI, but the Tag Library doesn't specify this and neither does the DTD/schema, so
>>> a locally controlled string value (e.g., "OSGBGridRef") wouldn't be formally invalid.
>>> 
>>> Hope this helps,
>>> 
>>> Terry
>>> 
>>> On Thu, 6 May 2010, Daniel Pitti wrote:
>>> 
>>>> I prefer the method described below by Mark, as the Ordnance Survey should have all of the
>>>> data you need, authoritatively maintained. Assuming the URI is persistent and that you
>>>> reference Bristol more than once in one or more finding aids, it will be more efficient
>>>> with respect to maintenance.
>>>> 
>>>> 
>>>> On May 6, 2010, at 3:16 PM, Mark A. Matienzo wrote:
>>>> 
>>>>> On Thu, May 6, 2010 at 12:18 PM, Jane Stevenson <[log in to unmask]> wrote:
>>>>>> I'll look at using authfilenumber. Maybe something like:
>>>>>> 
>>>>>> <geogname rules="ncarules" authfilenumber="ST590730">Bristol</geogname>
>>>>>> 
>>>>>> But specifying a source here would mean it applies to the place name, not the grid
>>>>>> reference.  I'm not sure how to provide the source/rules for both, as they are
>>>>>> different.
>>>>> Right, that's a good point. You could also use a method using the URI method, perhaps
>>>>> something like:
>>>>> 
>>>>> <geogname rules="ncarules"> Bristol <extptr linktype="locator" actuate="actuatenone"
>>>>> show="shownone" href="http://data.ordnancesurvey.co.uk/id/100mgridsquare/ST590730"/> 
>>>>> </geogname>
>>>>> 
>>>>> ** Note that this example URI isn't valid, as the Ordnance Survey hasn't yet provided a
>>>>> URI structure for 100 m grid references. 1 km grid references are valid, however.
>>>>> 
>>>>> Mark A. Matienzo Digital Archivist, Manuscripts and Archives Yale University Library
>>> Terry Catapano Special Collections Analyst/Librarian Columbia University Libraries Digital
>>> Program 212-854-9942 [log in to unmask]