On Fri, Aug 5, 2011 at 10:37 AM, Wichert Akkerman <[email protected]> wrote:
> On 08/05/2011 09:34 AM, w.p.w wrote:
>>
>> The default location field is useful in some ways and can be called from
>> other objects but is specific to some usecases (Server location,
>> geo-location etc) that said more and more nowadays we find that people want
>> there location to be shown for different sites so including it in the basic
>> metadata is a good idea for a modern system.
+1
>
> A big problem is that the location field has no defined syntax. People use
> it to store coordinates, names of places, descriptions of places, etc. That
with geospatial add on products like collective.geo the usage as a
descriptive field
becomes more apparent, so it is used to store a place name like
"Nairobi, Kenya".
(collective.geo uses this field to do geocoding i.e looking up the coordinates
for this location)
The coordinates itself are then stored as geospatial annotations, not in
the location field.
> makes it impossible for anything generic to use this field, making it in my
> opinion fit not for a standard (cataloged even) field.
dc.coverage is defined as geographical or temporal coverage - this is vague
I agree that cataloging this field does not make a lot of sense. there are
too few use cases (imho) for this
--
Best Regards,
Christian Ledermann
Nairobi - Kenya
Mobile : +254 702978914
<*)))>{
If you save the living environment, the biodiversity that we have left,
you will also automatically save the physical environment, too. But If
you only save the physical environment, you will ultimately lose both.
1) Don’t drive species to extinction
2) Don’t destroy a habitat that species rely on.
3) Don’t change the climate in ways that will result in the above.
}<(((*>
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
