Walter, Peter, and other interested parties,
Would the <ref> element with can take multiple values for its "target"
attribute would do the trick? with perhaps the "corresp" attribute of the
elements belonging to the pointer tag set to connect <div> and <ref>?
I'm not clear as to why the information needs to be encoded as the value
of an attribute of a <div> element. The TEI tag sets offer linking
mechanism that make it possible to express the relations between a given
<div> element and a given <ref> element containing the GIS metadata.
> "Peter C. Gorman" wrote:
> > We're producing an e-facsimile edition of a set of surveyors'
> > notebooks, in which individual notebooks will comprise <tei.2>
> > elements and entry sections will be represented as <div1>s. This
> > project is somewhat unusual in that the main access points will be
> > geographic areas rather than words in the text.
> > Has anyone else applied item-level GIS metadata to TEI texts?
> I had rather hoped someone else would take a stab at this (perhaps some
> did off list). In lieu of that could I offer a couple of thoughts,
> based on some consideration of this problem from an upcoming project...
> I would prefer not to add attributes to the <div1> element.
> Is there not one of the standard attributes intended to be used as
> external references?
> In other words, if there was an external intermediate data set linked to
> the GIS interface and with a key value that could be dropped into the
> the TEI file as a <div1> attribute, then you could do the necessary
> extract/transform for the search result.
> Walter Lewis
> [log in to unmask]
Francois Lachance, Scholar-at-large
20th : Machine Age :: 21st : Era of Reparation