The field names in general, the amenity=restaurant thing, that is not protected, i am sorry, but you cannot sue someone for copyright infringement if they copy that. forget it. It is the name of data structures and it is not a creative work, it is just a name.
see Baystate Holding: Technical Interfaces Not Copyrightable http://www.fenwick.com/docstore/publications/IP/IP_Articles/Baystate_Holding.pdf That is also why Microsoft created patents around its .net api to protected it, because there is no protection for an api. I can transform your description of the fields into a header file programmatically, and header files are not copyright-able. What is creative is the thing being described, the map or the restaurant etc, some people would claim that in USA that facts are also not copyright-able see also : http://www.winehq.org/pipermail/wine-devel/2001-February/000181.html Basically, you would be claiming that the choice of field names is somehow a creative work that somehow should be protected to ensure that such creativity is fostered. I say the choice of names is not creative, it is a just a convention for technical communication. Another project could choose synonyms for those words and list them, but then we would have to be able to map thiers onto yours, and you want to say it is illegal to do so? come on!! . mike On Wed, Oct 6, 2010 at 8:12 PM, Sam Vekemans <acrosscanadatra...@gmail.com> wrote: > On Wed, Oct 6, 2010 at 10:46 AM, M∡rtin Koppenhoefer > <dieterdre...@gmail.com> wrote: >> 2010/10/5 jamesmikedup...@googlemail.com <jamesmikedup...@googlemail.com>: >>> I want to say that header files and lists of field names are not >>> covered by copyright in general. >>> we could fight over textual descriptions, but the list of tages and >>> basic information is not seen as a copyright-able information. >>> Otherwise you would never be able to use a header file for programming. >>> mike >> >> >> I'm pretty sure that the complete system of OSM tagging (the OSM >> ontology) is covered by copyright (hence cc-by-sa) . This is not about >> "header files" IMHO. >> >> cheers, >> Martin >> > > Yup, > Which is why it's better to be updating the wiki instead of the chart > i made. The chart is usefull as a handy reference and has the ability > to extract and sort text out of it, and create an actual pdf catelogue > out of it. > I'll be reviewing the wiki map features again in a month or so, as im > sure it will be improved. By sorting the chart by > key/value/description/render samples etc. It makes it easy to see > where the gaps and inconsistencies are. (im also including a new > column for 'notes' to help with ideas to fix the wiki) > > For the other map feature charts that im making, im simply converting > the information from the source into this chart format. ... and > listing the most appropriate OSM tag that is recommended to be used > for each map feature. The CanVec set of map features is already > complete, as well as the linz and USGS and most of the TIGER features, > as well as most of the standard garmin features. > > So with the mapnik features, and potlatch, cyclemap, osmarender, > hikebikemap, josm features, im also making that into organized > spreadsheet format, as a way to easily sort and figure out where the > inconsistencies are across each feature ontology/schema > > So hopefully, for each osm-wiki page, it will get slowely fixed, so > then it will be able to cross-reference to what each of the mapfeature > datasets and renderers and softwares currently use in their respective > systems. > > Slightly grunt work, but it's needed in order for me to create a set > of standard map features .. all the while respecting both sides of the > copyright :-) (the CC-BY-SA map features, and the CC-BY map > features are 2 separate entities). All of the Dataset Map Features > that are (CCBY & PD) can be merged together, to form the SchemaTroll > MapFeatures set, where it uses the common terms across each set). And > so, this MapFeature set can freely be used as reference for > wiki-editors as well. :) ... just not the other way around. Since > ... obviously, ccBYsa is not backwards-compatable. :-) > > > Cheers, > Sam > -- James Michael DuPont Member of Free Libre Open Source Software Kosova and Albania flossk.org flossal.org _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
