From pierrec at progenysoftware.com  Mon Aug 30 07:42:58 2004
From: pierrec at progenysoftware.com (Pierre Cloutier)
Date: Mon Aug 30 08:48:31 2004
Subject: [Eac-l] EAC TL COMMENT
Message-ID: <6.1.2.0.0.20040830084159.03baad78@localhost>

Please consider a tag to allow encoding of latitude / longitude in the 
Place element.

Thanks.

Pierre Cloutier

From stephen.yearl at yale.edu  Mon Aug 30 09:15:41 2004
From: stephen.yearl at yale.edu (Stephen Yearl)
Date: Mon Aug 30 14:01:22 2004
Subject: [Eac-l] EAC TL COMMENT
In-Reply-To: <6.1.2.0.0.20040830084159.03baad78@localhost>
Message-ID: <5.2.1.1.2.20040830090521.0293fe00@sjy2.mail.yale.edu>

Pierre:

the place element is intended to cover both physical and non-physical
places, to which latitude and longitude information may not be applicable.
As such, if I remember correctly, it was though better not to overload the
element with a content model that privileged physical space.

does the following string syntax not work, though, as an attribute value 
for @valuekey?
http://www.edavies.nildram.co.uk/lat-long/version-1/lat-long-formal.html#LatLongString

regards,

St.

Stephen Yearl
Systems Archivist
Yale University Library::Manuscripts and Archives

At 08:42 AM 8/30/2004 -0300, you wrote:
>Please consider a tag to allow encoding of latitude / longitude in the 
>Place element.
>
>Thanks.
>
>Pierre Cloutier
>
>_______________________________________________
>Eac-l mailing list
>Eac-l@mailman.yale.edu
>http://mailman.yale.edu/mailman/listinfo/eac-l