RE: Licences, Ts&Cs, Permissions and Obligations

Phil,

I haven’t had time to delve into the POE work, but this may be useful.

Meteorology, Oceanography and Hydrology have a use case usually called “Resolution 40”. Much Met Ocean & Hydro data is collected, internationally, at public expense, for public safety, and should be made globally freely available to whoever wants it. It is called “Essential” data. There is a second category called “Additional”, which is usually higher resolution, more frequent and/or more up to date which usually better, but may have commercial value. The intent is to make this available in the same way as Essential, but the provider reserves the right to ‘pull it’ from public dissemination if it can be demonstrated that a third party is using it in the original providers’ area of economic interest and causing economic damage.

The third category of data is called “Other” and can have commercial terms, and is generally used for ‘value added’ services over and above that required for public safety warnings. E.g. warning ships and aircraft of potentially dangerous conditions would be Essential, but telling ships and aircraft how much fuel to carry for a specific route and time, to optimise costs, would be ‘Other’

The exact phrasing is at Page 18 of https://www.wmo.int/pages/about/documents/WMO837.pdf


The hydrology policy is actually called Resolution 25 http://www.wmo.int/pages/prog/hwrp/documents/Resolution_25.pdf


HTH, Chris

From: Rob Atkinson [mailto:rob@metalinkage.com.au]
Sent: Monday, June 13, 2016 7:29 PM
To: Phil Archer; SDW WG Public List
Subject: Re: Licences, Ts&Cs, Permissions and Obligations

Hi Phil

this may or may not be relevant - but in Australia there is some uncertainty about the use of postcodes, and what obligations would apply if this was used in a web context - either as a service parameter or in a response payload

http://auspost.com.au/business-solutions/postcode-data.html


says "You will need a licence to use the Australian postcode list for commercial or business purposes."

what if you had a dataset that had a postcode for every address - you could reverse engineer the list of postcodes from any comprehensive address set.

The issue is is not so much the licence regime, whatever you may think of it, as the fact that the casual user or web developer would certainly not expect such a situation arising from a publically owned service in the 21st century - so i guess this is the sort of use case where the machinery needs to be able to bring it to attention based on metadata.

Cheers
Rob Atkinson

On Tue, 14 Jun 2016 at 02:13 Phil Archer <phila@w3.org<mailto:phila@w3.org>> wrote:
Dear all,

This isn't related to current work items within the WG but I believe it
will be of relevance to at least some folks here.

One of my other WGs is the Permissions and Obligations Expression WG who
ask whether you have a use case arising from your work where you are
hindered by a lack of info about the terms and conditions of use of some
data. The group is collecting its use cases on its wiki [1] and deriving
requirements [2]. They not starting from scratch. This work has a long
history, including time as a Community Group, and the existing ODRL spec
is well implemented [3], so we're looking for use cases that ODRL
doesn't handle.

Interestingly, the issue of subsetting came up today :-)

Shout in my general direction for more info if needed.

Cheers

Phil

[1] https://www.w3.org/2016/poe/wiki/Use_Cases

[2] https://www.w3.org/2016/poe/wiki/Requirements

[3] https://www.w3.org/community/odrl/


--


Phil Archer
W3C Data Activity Lead
http://www.w3.org/2013/data/


http://philarcher.org

+44 (0)7887 767755
@philarcher1