> Ideally we should support both explicit
> and implicit in the same record i.e. use multiple
> DC:coverages, preferably leveraging the recommendations of
> GAP and reconciling DC and ISO worlds to best effect !
Just to clarify (in terms of the DC Abstract Model and RDF), if there is one area of coverage then you should provide a single dc:coverage property with multiple 'value strings' ("London, UK" and "N 51° 30' 30''W 0° 7' 31''" or whatever). Multiple dc:coverage properties imply multiple areas of coverage (or, at best, it is ambiguous if you mean one area of coverage or multiple areas).
Unfortunately, providing multiple value strings isn't possible in Simple DC systems like the OAI-PMH oai_dc syntax - so if that is how you are shifting metadata about then you have to fall back to the use of multiple dc:coverage properties (and the resulting ambiguity :-( ).
Andy.
> cheers
>
> James S Reid
> EDINA (Geoservices)
> Uniiversity of Edinburgh
>
> tel:+44 (0) 131 651 1383
> mob: 0759 5116988
>
> "Walking down the road
> With a blade in your waist
> Johnny you're too bad, Johnny you're too bad"
>
> John Martyn 11th September 1948 - 29th January 2009
>
>
>
> Rosemary Russell wrote:
> > I got some feedback from Maurice Vanderfeesten at SURF who
> coordinates
> > the DRIVER guidelines - the DC:Coverage recommendation was
> apparently
> > inherited from previous DAREnet work and no alternative suggestions
> > were received during the consultation period. However the
> guidelines
> > are always open to suggestions for improvement (thanks for
> this one),
> > and the plan is to make the guidelines available in a wiki
> to enable
> > easier management of updates and version control - there will be a
> > 'comment' facility for each page. SURF is currently running a test
> > version - I've forwarded your email in the meantime.
> >
> > Regards, Rosemary
> >
> > James S Reid wrote:
> >> Could somebody on the list shed some light on why the DRIVER
> >> guidelines state that for DC:Coverage the " Recommended
> best practice
> >> is to select the value from a controlled vocabulary (for
> example, the
> >> Getty Thesaurus of Geographic Names or TGN) and that, where
> >> appropriate, *named places or time periods be used in
> preference to
> >> numeric identifiers as*, for example, sets of co-
> ordinates or date
> >> ranges. If necessary, repeat this element to encode multiple
> >> locations or periods."
> >>
> >> This is at odds with what we have been encouraging for years
> >> (favouring explicit georeferencing via no-ambiguous coordinate
> >> referencing) as part of having the JISC IE georeferenced
> and indeed
> >> is guaranteed to provide ambiguity e.g. the placename
> 'london' is not
> >> non-ambigous were as N 51° 30' 30''W 0° 7' 31'' is (this is the UK
> >> London as opposed to the Canadian one at N 42° 59' 0''W
> 81° 13' 58' ).
> >>
> >> See also our GAP work -
> >>
> http://www.ukoln.ac.uk/repositories/digirep/index/Geospatial_Applicat
> >> ion_Profile
> >>
> >>
> >> ??
> >>
> >>
> >>
> >> James S Reid
> >> EDINA (Geoservices)
> >> Uniiversity of Edinburgh
> >>
> >> tel:+44 (0) 131 651 1383
> >> mob: 0759 5116988
> >>
> >> "Walking down the road
> >> With a blade in your waist
> >> Johnny you're too bad, Johnny you're too bad"
> >>
> >> John Martyn 11th September 1948 - 29th January 2009
> >>
> >>>
> >>
> ---------------------------------------------------------------------
> >> ---
> >>
> >> The University of Edinburgh is a charitable body, registered in
> >> Scotland, with registration number SC005336.
> >>
> >
> >
>
> --
> The University of Edinburgh is a charitable body, registered
> in Scotland, with registration number SC005336.
>
|