- From: Peter Baumann <p.baumann@jacobs-university.de>
- Date: Sat, 25 Apr 2015 19:22:14 +0200
- To: <Kerry.Taylor@csiro.au>, <l.vandenbrink@geonovum.nl>, <public-sdw-wg@w3.org>
- Message-ID: <553BCD46.1080503@jacobs-university.de>
Hi community,
now I managed to do the additions, see page
https://www.w3.org/2015/spatial/wiki/Cov_References
That has also prompted me to leave some ideas on the wishlist page as well.
Hope it helps to get an overview, I'll gladly clarify where you find necessary.
cheers,
Peter
On 04/15/15 14:27, Kerry.Taylor@csiro.au wrote:
>
> Yes, please, Peter! +1 Ideally, not just a reference but a sentence or a
> paragraph explaining what the reference has in that we need to know.
>
>
>
> Kerry
>
>
>
> *From:*Peter Baumann [mailto:p.baumann@jacobs-university.de]
> *Sent:* Wednesday, 15 April 2015 8:32 PM
> *To:* Linda van den Brink; SDW WG (public-sdw-wg@w3.org)
> *Subject:* Re: More detailed requirements
>
>
>
> perfect - thanks, Linda! I will go this avenue.
> -Peter
>
> On 04/15/2015 12:23 PM, Linda van den Brink wrote:
>
> Hi Peter,
>
>
>
> +1 for a page describing the capabilities of existing standards. I think
> the right place is already on the wiki (correct me if I’m wrong anyone).
>
>
>
> You can find it under
> https://www.w3.org/2015/spatial/wiki/Main_Page#Work_in_Progress. For each
> of the four main deliverables, there’s a page XXX References, e.g.
> https://www.w3.org/2015/spatial/wiki/Cov_References. There’s already an
> entry for WCS there. You could create a sub page linked from there where
> the capabilities are described.
>
>
>
> Linda
>
>
>
> *Van:*Peter Baumann [mailto:p.baumann@jacobs-university.de]
> *Verzonden:* woensdag 15 april 2015 12:14
> *Aan:* Linda van den Brink; SDW WG (public-sdw-wg@w3.org
> <mailto:public-sdw-wg@w3.org>)
> *Onderwerp:* Re: More detailed requirements
>
>
>
> Dear Linda, all,
>
> it's exciting to follow this discussion. Incidentally, OGC Big Geo Data
> standards, WCS and WCPS, already have some answers, and their concepts are
> of course independent from the syntactic wrapper, so they can be
> transposed into RDF world as well.
>
> Question: can we have, in parallel to the requirements collection, a page
> describing the capabilities of existing standards so that a matching can
> be accomplished by referencing? Might ease to find white spots on the map,
> as well as reaping the benefits of existing accomplishments?
>
> I can gladly start such a page, but as a newbie I am glad to get pointed
> to the right place for doing that.
>
> cheers,
> Peter
>
>
> On 04/15/2015 12:00 PM, Linda van den Brink wrote:
>
> Hi all,
>
>
>
> As I mentioned in a separate email we (Geonovum) are currently
> reviewing the requirements and trying to make sense of them and add
> more detail to them. This is a little bit ahead of the work of the
> SDWWG, but I think could be relevant to the question of how to
> structure the UCR document. As an example, please find below one
> requirement with our questions and more detailed sub-requirements.
>
>
>
> 1. It should be easy to find spatial data on the web
>
> 1.1 Non-experts should be able to find spatial data on the
> web through free-text searches
>
> 1.2 Spatial data on the web - datasets as well as single
> objects - should be findable through numerous ontologies/synonyms
>
> 1.3 Popular search engines should be able to find spatial
> data on the web (see requirement #5)
>
> 1.4 It should be possible to add semantics and structure to
> spatial data on the web (through existing mechanisms e.g. schema.org,
> Location Core)
>
> 1.5 Human/computer search mechanisms must be able to search
> for spatial entities/objects within datasets
>
> 1.6 There should be standardized search filters (e.g.
> within, nearby) for spatial data that are supported by popular search
> engines
>
> 1.7 Spatial objects should be findable through a (set of)
> basic/primitive spatial property e.g. centroid (see requirement #2).
>
> 1.8 Metadata should be inseparable from the data it describes
>
> 1.9 It should be possible for users to annotate (add tags
> and links to other datasets) the (meta)information they find (so that
> search is improved)
>
> 1.10 APIs and “smart” geo-services (e.g. WPS, WFS) should be
> (made) crawlable
>
>
>
> Questions about this requirement:
>
> - What are the problems of current data finding mechanisms?
> Is it lack of suitable technologies or lack of robust governance
> structures (i.e. high quality publishing process, robust maintenance
> process, etc.)? One problem could be that spatial data is published
> through mechanisms that are not in itself crawlable. E.g. WFS services
> or atom feeds (in non-standard formats). See also last bullet.
>
> - Through what mechanism is the entity (human/machine)
> searching for data? Centralized registers? Decentralized (but linked)
> registers? Free-text searches? (in our opinion at least free text search)
>
> - Which data/information properties are queried: keywords,
> extent, timespan, free-text fields, crowdsourced tags, location (using
> spatial operators), zoom level/resolution/level of detail, coordinate
> system, place name, license?
>
> - How should APIs and “smart” geo-services (.e.g WFS) be indexed?
>
>
>
> We have similar sub-requirements (and questions) about several of the
> other requirements, but have not quite gotten through the list. Should
> we put all this somewhere on the wiki?
>
>
>
> Linda
>
> *______________________________________*
>
> *Geonovum*
>
> *Linda van den Brink*
>
> /Adviseur Geo-standaarden/
>
>
>
> *a*: Barchman Wuytierslaan 10, 3818 LH Amersfoort * *
>
> *p*: Postbus 508, 3800 AM Amersfoort
>
> *t*: + 31 (0)33 46041 00
>
> *m*: + 31 (0)6 1355 57 92
>
> *e: *l.vandenbrink@geonovum.nl <mailto:r.beltman@geonovum.nl>
>
> *i*: www.geonovum.nl <http://www.geonovum.nl/>
>
>
>
>
>
>
> --
>
> Dr. Peter Baumann
>
> - Professor of Computer Science, Jacobs University Bremen
>
> www.faculty.jacobs-university.de/pbaumann <http://www.faculty.jacobs-university.de/pbaumann>
>
> mail: p.baumann@jacobs-university.de <mailto:p.baumann@jacobs-university.de>
>
> tel: +49-421-200-3178, fax: +49-421-200-493178
>
> - Executive Director, rasdaman GmbH Bremen (HRB 26793)
>
> www.rasdaman.com <http://www.rasdaman.com>, mail: baumann@rasdaman.com <mailto:baumann@rasdaman.com>
>
> tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
>
> "Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)
>
>
>
>
>
>
>
> --
> Dr. Peter Baumann
> - Professor of Computer Science, Jacobs University Bremen
> www.faculty.jacobs-university.de/pbaumann <http://www.faculty.jacobs-university.de/pbaumann>
> mail: p.baumann@jacobs-university.de <mailto:p.baumann@jacobs-university.de>
> tel: +49-421-200-3178, fax: +49-421-200-493178
> - Executive Director, rasdaman GmbH Bremen (HRB 26793)
> www.rasdaman.com <http://www.rasdaman.com>, mail: baumann@rasdaman.com <mailto:baumann@rasdaman.com>
> tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
> "Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)
>
>
--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen
www.faculty.jacobs-university.de/pbaumann
mail: p.baumann@jacobs-university.de
tel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Bremen (HRB 26793)
www.rasdaman.com, mail: baumann@rasdaman.com
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)
Received on Saturday, 25 April 2015 17:22:48 UTC