W3C home > Mailing lists > Public > public-sdw-wg@w3.org > June 2015

RE: simplicity or web developer friendliness as requirements?

From: <Kerry.Taylor@csiro.au>
Date: Wed, 3 Jun 2015 14:23:19 +0000
To: <stefan.lemme@dfki.de>, <public-sdw-wg@w3.org>
Message-ID: <3CD3C8BBF0D87B4D8154C3978732049C50F46CC3@exmbx05-cdc.nexus.csiro.au>
I, too,  am totally on side with this aim.

Currently, we have it recorded here https://www.w3.org/2015/spatial/wiki/BP_Principles

I think it sits much more readily as an overarching goal of our other (non UCR)  deliverables rather than a requirement – hence a “principle” (and expected to go into the introduction of our BP document) , although it is explicit in some Use cases (e.g. 4.37 Landsat data services).

Perhaps @Linda, or @Stefan, you could have a go at drafting  this as you would like to see it adopted on that wiki page (a few alternatives would be fine) , and we can bring this back for resolution?  When you are ready please raise this as an issue and ask for it to go on agenda soon (as it is important context for the BP).


From: Stefan Lemme [mailto:stefan.lemme@dfki.de]
Sent: Wednesday, 3 June 2015 9:10 PM
To: public-sdw-wg@w3.org
Subject: Re: simplicity or web developer friendliness as requirements?

I do feel strong about the "web developer friendliness" too, but more from the point of using/incorporating spatial data (when I was already able to find it) and not so much about the publishing part.

In particular, I would consider here that respective services offer web-friendly delivery formats (i.e. natively supported image formats for raster data, (compatible/declarative) 3D formats for vector data, etc.).
In order to maximize the pickup of spatial data by non-experts, such as 3D-application and web developers, we need to ensure a very low entrance barrier.

As pointed out by Linda, simplicity in fact might be not requirement specific to spatial data, but it is obvious that currently spatial data lacks of an approach to fulfill this requirement while other kinds of data (e.g. 3D in general) tries to specifically address this issue.


On 6/2/2015 8:44 AM, Linda van den Brink wrote:
I do feel strongly about capturing this as a principle or requirement or in some other way so that it’s clear we think this is important. Spatial data on the web should be easy to find,  use and to publish by non-experts. While strictly this is maybe not a spatial requirement, it is my feeling that nowadays spatial data is NOT easy to find, use and publish by non-experts. So it’s important to address this.

I put something on  the BP Principles page about simplicity a while ago. Wasn’t sure if it fit there, but it is, as Frans writes, more of a general principle and not a specific requirement.

There’s also another aspect to simplicity we should address: Our deliverables should be easy to use by web developers.


Van: Alejandro Llaves [mailto:allaves@fi.upm.es]
Verzonden: maandag 1 juni 2015 18:56
Aan: Ed Parsons
CC: SDW WG Public List; Frans Knibbe
Onderwerp: Re: simplicity or web developer friendliness as requirements?

El 1/6/2015 6:15 p. m., "Ed Parsons" <eparsons@google.com<mailto:eparsons@google.com>> escribió:
Hi All,

I agree with the sentiment, we should aspire for simplicity and recognise a broad community of users outside the traditional geospatial community - Maybe however this is best captured in the next deliverable the BP document ?


On Mon, 1 Jun 2015 at 16:27 Frans Knibbe <frans.knibbe@geodan.nl<mailto:frans.knibbe@geodan.nl>> wrote:
Dear friends of spatial data on the web,

There have been several calls for inclusion of requirements for simplicity in the UCR document. While I think simplicity is an extremely important aspect of system design, it seems to be a very general principle, something not exclusively spatial. For that reason I think we can't have requirements like 'spatial data on the web should be easy to use' in the UCR document.

It is also possible to find some more narrowed down calls for simplicity, focused on web developers particularly, asking for JSON and JQuery support for example, or saying that expertise on geographic data should not be necessary to work with spatial data on the web. I wonder if it is possible to define a functional requirement in the UCR document if this focus is applied. But again, compliance with existing standards and best practices for web development is hard to view as something inherently spatial.

Are there people that feel strongly about having a requirement for simplicity or web developer friendliness in the UCR document? If so, can you suggest a way to phrase such a requirement so that it is clearly in scope for the SDWWG?


Frans Knibbe
President Kennedylaan 1
1079 MB Amsterdam (NL)

T +31 (0)20 - 5711 347<tel:%2B31%20%280%2920%20-%205711%20347>
E frans.knibbe@geodan.nl<mailto:frans.knibbe@geodan.nl>


Ed Parsons
Geospatial Technologist, Google

Mobile +44 (0)7825 382263<tel:%2B44%20%280%297825%20382263>
www.edparsons.com<http://www.edparsons.com> @edparsons

Received on Wednesday, 3 June 2015 14:24:12 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:17 UTC