Re: [Spatialml-discussion] some comments

[Hitzeman, J. M. <hi...@mi...>]

In annotating using SpatialML, I have found there to be a natural
difference between LINKs and PATHs.  LINKs are used to pinpoint a PLACE
while PATHs are used to give directions on how to get to a PLACE.  The
signals for a LINK, when present, are never more complicated than the
possible linkTypes.  [Boston, MA] is the same as [Boston in MA] and the
relationship is clearly indicated by IN.  Similarly, [Boston (42.358=B0N
71.060=B0W)] indicates an EQ relationship between Boston and its =
latlong;
The signals, if any, are the two parens.  In contrast, the PATH
indicates a relationship between two distinct places, two pins on a
map.  The signals have more semantic content than the finite list of
linkTypes. If I tell you that I live in the house with the blue door
across from the Commonwealth Pool, I've LINKed my house with the house
with the blue door (one pin) and I've given you a PATH between the Pool
(pin#1) and the house (pin#2) so that if you can find the pool you have
instructions on how to find my house.

PATHs are particularly useful if you're looking for a PLACE that
doesn't have coordinates in any gazetteer, e.g., [We put down anchor
five miles off of the port of Leith.]  If you can find the latlong for
Leith, you can guess at the latlong for our location.  A LINK gives a
much greater search space, e.g., [We put down anchor in the Waters of
Leith.]

Janet

-----Original Message-----
From: spa...@li...
[mailto:spa...@li...] On Behalf
Of Greg Jan=E9e
Sent: Wednesday, April 18, 2007 3:27 PM
To: spa...@li...
Subject: [Spatialml-discussion] some comments

2. PLACEs identify (by surrounding with XML tags) relevant portions =20
of the document.  PATHs do, too, via SIGNALs.  But LINKs don't.  =20
Perhaps, by symmetry, they should?  For example, a LINK could surround
the relevant preposition ("in") or punctuation (",").

[snip]