See also: IRC log
This was one of two parallel meetings held so that the WG could divide its work up most efficiently. This one focused on the requirements relevent to the Best Practices document, the other focused on the other deliverables.
<eparsons> All Hangout URL for this call will be https://plus.google.com/hangouts/_/event/ce2gg0fbtug4q7urls3u211gj1c
<phila> chair; Ed
<eparsons> scribe: clemens
<phila> scribe: ClemensPortele
<eparsons> http://www.w3.org/2015/03/25-sdw2-minutes.html
JoshLieberman: Mention on fine grained metadata - can you expand?
eparsons: How much would we need to beyond what was happening on the web in general...
JoshLieberman: could be about resolution and other metadata related to spatial aspects
eparsons: Need to revisit this when we get back to the requirements
<JoshLieberman> Was just about to ask that! Spatial is often out ahead...
<AndreaPerego> Can you hear me?
<Linda> no we cant'
<AndreaPerego> yep
<JoshLieberman> Getting some ...breathing on the line.
AndreaPerego: regarding requirements not just related to spatial and which are more general - we may need to do something specific in spatial with general concepts; URIs may be an example
<Linda> +1
<eparsons> +1
<phila> RESOLVED: Last week's minutes accepted http://www.w3.org/2015/03/25-sdw2-minutes.html
<phila> http://www.w3.org/2015/spatial/track/actions/open
<AndreaPerego> https://www.w3.org/2015/spatial/wiki/Minutes_from_Best_Practice_deliverable_group#Summary_of_Action_Items
AndreaPerego: Open actions in the Barcelona meetings, but not in the tracker (on Chaals and Clemens)
eparsons: requires spatial
ontology and URIs
... metadata, too
... api not really discussing dissemination of the data
JoshLieberman: provenance is important, too
phila: not going to put into the docs that you should enable geo-location when tweeting about an earthquake
JoshLieberman: do virtual observations apply to this?
eparsons: is that a requirement that is in the use case or are we extending it?
eparsons: an issue of scale, more than anything else. Is that really different that we need to address or do we just to be clear not to be scale-specific?
JoshLieberman: Key is that this is not about a geo-centric reference system
<AndreaPerego> Maybe it's just about describing the "shape" of an entity, and not to locate it.
eparsons: current requirement about ref system not sufficient to capture the "metaphysical" aspects
<scribe> ACTION: Josh to come up with a sentence that captures the UC 43 discussion [recorded in http://www.w3.org/2015/04/01-sdw2-minutes.html#action01]
<trackbot> Sorry, but no Tracker is associated with this channel.
phila: time aspect in this use case?
<JoshLieberman> Requires not just a coordinate reference system but also an authoritative reference to the space or object that data is being positioned within / upon
phila: Probably the other group will deal with this (Erich is there, too)
Discussion about the term "authoritative reference". Maybe change to "global reference"?
<AndreaPerego> +1
eparsons: from a best practice point of view, not new is apparent
<eparsons> ok thx phil
AndreaPerego: extension to
general metadata standards in Europe (for geospatial and
statistical data); touches several of the topics discussed
before - CRS, geometries, ...
... Also data quality (not necessarily specific to
spatial)
... probably no new requirements, just supporting the need for
a couple already identified
... However, one question is how to model something in a
non-domain-specific way (level of detail vs spatial
resolution); what are the design patterns for this?
<Zakim> phila, you wanted to talk about data quality and URI design
<phila> DCAT
phila: would be good if this group could provide input to work on extensions to DCAT for spatial
<phila> Recommendations on the use of HTTP URIs for geospatial data and metadata
JoshLieberman: lots of work on
metadata, many standard; also depends on the viewpoint what is
called metadata
... best practice should focus on simple things (e.g., how to
find bounding box when following a link)
AndreaPerego: How to make spatial data more discoverable using general search engines? Use of HTML, RDFa, microdata, etc
<phila> Columns F & J are relevant here
eparsons: related to other use case, but less about recommendation when creating new resources, more about enabling existing resources
AndreaPerego: Not necessarily restricted to search engines, could also be other web applications
JoshLieberman: related to RESTful
APIs?
... in the sense of landing pages
<stlemme> in fact there are four UCs
<stlemme> in fact there are four UCs remaining
eparsons: send comments on the
other use cases via email
... next week single meeting again
... face-to-face meeting will be at TPAC in Japan
phila: either Mon/Tue or Thu/Fri
Linda: When will this be decided?
phila: will work with chairs on this
<phila> TPAC 2015 venue
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Ed/eparsons/ Succeeded: s/Let's move one// Succeeded: s/Eric/Erich/ Found Scribe: clemens Found Scribe: ClemensPortele Inferring ScribeNick: ClemensPortele Scribes: clemens, ClemensPortele Present: Andrea Clemens Ed Josh Linda Matt Phil stlemme Got date from IRC log name: 01 Apr 2015 Guessing minutes URL: http://www.w3.org/2015/04/01-sdw2-minutes.html People with action items: josh WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]