[OSM-dev] Attribution string (was: Licence redaction ready to begin)

Igor Brejc igor.brejc at gmail.com
Thu Jul 12 07:45:38 BST 2012


Why not use TileJSON?  http://mapbox.com/developers/tilejson/

Igor

On Thu, Jul 12, 2012 at 7:12 AM, Kai Krueger <kakrueger at gmail.com> wrote:

>  On 07/10/2012 01:38 PM, Lynn W. Deffenbaugh (Mr) wrote:
>
> I've been wondering if it would be possible to put a fixed URL on the tile
> and/or API servers that application programs could fetch to retrieve the
> current attribution string for that particular tile server?  Something like
> 0/0/0.txt or some-such that we could simply code into the tile-based
> clients to fetch the desired string instead of coding it directly in the
> clients?
>
> I think this sounds like a good idea. Rather than 0/0/0.txt, I would use a
> name like attribution.txt or license.txt in the base directory of the tile
> style. It allows for different attribution for different styles on the same
> server while still having a meaningful name.
>
> In addition I would suggest to add an attribution.html that has the
> attribution string as a html snippet with the correct hyperlink to the
> license and contributors.
>
> If people think this is useful, I could add this to mod_tile to help
> standardize the attribution URL.
>
> Kai
>
>
> Since we all have to go in and change the attribution anyway, now might be
> a really good time to make it a fetchable string.
>
> Lynn (D) - KJ4ERJ
>
> PS.  I'm proposing a plain text string that can then be integrated into a
> client display here.  Another fixed URL per tile server could provide the
> reference URL string so that said applications can make the text
> attribution a link going there.
>
> On 7/10/2012 3:32 PM, Michael Collinson wrote:
>
> Hi Paul,
>
> We discussed this tonight at LWG
> https://docs.google.com/document/pub?id=1W7eh17a7cEUilpbictKYnWJfHoxIcA1W_tPEmqvmDkcitem 5
>
> We do not think temporary dual-licensing is particularly practical or
> necessary provided that we allow consumers reasonable time to make their
> attribution string changes. We are happy to re-visit this if there is any
> strong reason we are not seeing.
>
> Mike
> LWG
>
> >* From: Richard Fairhurst [mailto:richard at systemeD.net <http://lists.openstreetmap.org/listinfo/dev>]*>* Subject: [OSM-dev] Licence redaction ready to begin*>* *>* Once it is complete, we will be ready to distribute data under the ODbL*>* and we'll advise of that with a separate announcement. The final pre-*>* redaction dataset available under CC-BY-SA has now been generated at*>* http://planet.openstreetmap.org/planet-120704.osm.bz2 . Where data has*>* been redacted, any attempt to access it from the API or the site's*>* 'browse' pages will return a response to that effect.*
> To transition from tiles derived from a CC BY-SA source to tiles derived
> from a ODbL source will require changing the attribution and regenerating
> all tiles so that CC BY-SA data is not mis-represented as being ODbL data.
> What time period will data be available under dual licenses so that tile
> servers will not have to reload their database then immediately delete every
> cached tile when changing their attribution?
>
> When I discussed this with Frederik awhile back I suggested publishing the
> first post-redaction planet as dual-licensed as well as one week of diffs to
> allow tile servers to continue to serve old CC BY-SA tiles and re-render
> over the course of a week.
>
> At the very least I would suggest distributing the first post-redaction
> planet as dual-licensed for the simple reason that all the information to
> create it will be available as CC BY-SA.
>
>
>
>
> _______________________________________________
> dev mailing listdev at openstreetmap.orghttp://lists.openstreetmap.org/listinfo/dev
>
>
>
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20120712/a5f3360d/attachment.html>


More information about the dev mailing list