In the GLUE Specification v. 2.0, page 8, it is specified the Entity class.
In its "Association.End" there is just one field: "Extension.Key", but in
the Extension class, its unique identifier is "LocalId". So in the Entity
class, it should be specified "Extension.LocalId" instead of
"Extension.Key". "Extension.Key" shouldn´t be used because of its
description, which I quote here: "This identifier is not required to be
unique; several instances of this class MAY hold the same value of this
attribute".
So this could be another erratum, isn´t it?
Regards,
David
--
David Horat
Software Engineer specialized in Grid and Web technologies
IT Department – Grid Deployment Group
CERN – European Organization for Nuclear Research » Where the web was born
Phone +41 22 76 77996
http://davidhorat.com/http://cern.ch/horathttp://www.linkedin.com/in/davidhorat
Hi all,
There's an interesting audio interview with Tyler Bell on O'Reilly Radar about
how to specify geographical location. In the interview, Tyler talks about
Yahoo's approach:
http://radar.oreilly.com/2009/04/where-20-preview---tyler-bell.html
In brief, they define a unique 32-bit number to each location: the "Where On
Earth ID" or "WOEID". They also provide a public, restful API to query their
database to extract metadata about the area. Details are available here:
http://developer.yahoo.com/geo/http://developer.yahoo.com/geo/guide/
One of the nice features of this is one can express low-granularity
information (such as a city, county or country) without having to specify a
(potentially meaningless) centroid lat./long. ordered pair. This is nice as
they also expose their semantic structure, so one can (for example) discover
that Canada is within the United States.
I propose in the next version of GLUE we add an optional field called woeid so
people have a standard field to include the WOEID, if they choose to do so.
Cheers,
Paul.
