Ok maybe think of it this way...

In the OSM community, our 'attribution' is simple: check who is listed
as the author, then you know who to complain too if you see problems.

For attribution of a 'data supplier', just contacting the person who
'copied-in*' the data, doesnt help.

Our solution is to have the "it wasnt me that made the data" tag, so
then it allows automatic approval if someone wants to  change or
remove it.

Hope that makes sence,

cheers,
Sam

On 11/19/09, Sam Vekemans <acrosscanadatra...@gmail.com> wrote:
> Hi Steve,
>
> The reason i didnt include attribution as part of the changeset is
> because .... I didnt know how. :)
>
> i chose to put the 'attribution' tag on each point, line, area map
> feature, so that way, anyone editing will immediatly see where it came
> from.
>
> I believe that that is the point of 'attribution'. (and the licence
> agreement)
>
> However, because attribution can be added to the changeset, i think it
> ALSO should be there (where practicle todo so)
>
> The attribution in the form of 'cross refrencing' with tags prefixed
> with the name of the source. Are not need. This does not add value to
> the map. However, the human readable canvec:CODE adds value, because
> all the 'like' objects in the map can be modified all at the same
> time.
>
> Hence, why the USA TIGER tags are being removed. (the ones that have
> no value) the tag 'attribution' remains.
>
> Cheers,
> Sam
>
> On 11/19/09, Steve Singer <ssinger...@sympatico.ca> wrote:
>> On Tue, 17 Nov 2009, James Ewen wrote:
>>
>>> We as the OSM community have chosen to accept the restrictions in
>>> order to be able to import HUGE amounts of data, but it leaves us with
>>> a quandary... how much modification of the imported data needs to
>>> happen BEFORE the attribution can be REMOVED?
>>
>> When we started importing the geobase data we took the safe approach and
>> attribute each way.  The idea being that with all that attribution no one
>> could argue that we are not complying with the geobase terms.  However I
>> can't recall if anyone has said that this level of attribution is
>> actually
>> required by the geobase license.
>>
>> Maybe someone with better license reading skills than myself or Sam can
>> figure out what the minimum level of attribution is actually required.
>>
>> From a license point of view:
>>
>> Is putting the attribution in the changeset tags sufficient to comply
>> with
>> the license?
>>
>> Is putting the attribution on the wiki data sources page sufficient to
>> comply with the license?
>>
>>
>>
>>>
>>> James
>>> VE6SRV
>>>
>>> _______________________________________________
>>> Talk-ca mailing list
>>> Talk-ca@openstreetmap.org
>>> http://lists.openstreetmap.org/listinfo/talk-ca
>>>
>>
>>
>> _______________________________________________
>> Imports mailing list
>> impo...@openstreetmap.org
>> http://lists.openstreetmap.org/listinfo/imports
>>
>
>
> --
> Twitter: @Acrosscanada
> Blog:  http://Acrosscanadatrails.blogspot.com
> Facebook: http://www.facebook.com/sam.vekemans
> Skype: samvekemans
> OpenStreetMap IRC: http://irc.openstreetmap.org
> @Acrosscanadatrails
>


-- 
Twitter: @Acrosscanada
Blog:  http://Acrosscanadatrails.blogspot.com
Facebook: http://www.facebook.com/sam.vekemans
Skype: samvekemans
OpenStreetMap IRC: http://irc.openstreetmap.org
@Acrosscanadatrails

_______________________________________________
Talk-ca mailing list
Talk-ca@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-ca

Reply via email to