I think it's time to think about the specification. My idea is to create a format which we can use to import rules from existing projects to, collect and process them all united and then export then back to the various formats used by several projects. The specification therefore is the "bridge" between those formats and connects them (connecting different worlds together).

The import/export procedures can be coordinated through Bots. The discussion about how the spec should look like happens in the "specification" channel on Slack Workspace https://join.slack.com/t/tagtransform/shared_invite/enQtODYzNjEzMTk1NjgxLTdiMDZlOWQzNjE0M2Y4OTE2M2E4MzQ1N2Q4MjhlYjNjZmRmMmVjNjk3ZjIyZTAzNmZiMWU1Y2IyYTUxZjRmNGI and summaries/updates of the outcome of the discussion will be provided in https://github.com/ValorNaram/transformation-table-osmtags/issues/4 because Slack does not provide any good method to summarize discussions (so far I know).

I've made a first Draft of the specification which can be viewed at https://github.com/ValorNaram/transformation-table-osmtags/tree/master/spec . If you want to provide improvements then do a Pull Request or join Slack.

Cheers

Sören Reinecke alias Valor Naram


-------- Original Message --------
Subject: Re: [OSM-dev] tagtransform for OSM - An effort make tagging and using OSM data easier; bridging different worlds together
From: Sören Reinecke via dev
To: Mateusz Konieczny
CC: Dev


Nothing is wrong with GitHub issues but GitHub has limitations when it comes to instant team talks. Slack allows to open subthreads when a point from someone needs to be negotiated. And that allows more deep communication and organisation.


-------- Original Message --------
Subject: Re: [OSM-dev] tagtransform for OSM - An effort make tagging and using OSM data easier; bridging different worlds together
From: Mateusz Konieczny
To:
CC: Dev


What is wrong with GitHub issues?

Can be followed easily, are not a resource hog
and do on.

(Maybe I am unusual that I use Slack rarely
and most of others are usually on Slack)


12 Dec 2019, 17:36 by dev@openstreetmap.org:
Hi all,

I've now set up a Slack Workplace for further discussion and work. Ask me and I will invite you.

Cheers

Sören Reinecke alias Valor Naram


-------- Original Message --------
Subject: Re: [OSM-dev] tagtransform for OSM - An effort make tagging and using OSM data easier; bridging different worlds together
From: Sören Reinecke via dev
To: dev@openstreetmap.org
CC:


Hi Gerd,

nice to hear your heartbeat for tagtransform. Take a look at the GitHub issue https://github.com/ValorNaram/transformation-table-osmtags/issues/3 where I wrote down the infrastructure I'm planning. There I mention also the use of bot script to automatically collect rules from various validators and rule databases and to convert these to the format tagtransform uses to unify data from different sources. This allows the modification and the convert back to all the other formats used by different programs. This way we create a sustainable and good ecosystem of validation rules.

The way the team I want to set up communicates and exchanges is GitHub and Slack. On GitHub we will first work in my repository, later on we can create an organisation and move the repo. In Slack I need to create a workplace and figure out how moderation in Slack works.

Cheers

Sören Reinecke alias Valor Naram


PS: This content is of public interest that's why this e-mail belongs to this list.

-----Original Message-----
From: Gerd Petermann <gpetermann_muenc...@hotmail.com>
Subject: Re: [OSM-dev] tagtransform for OSM - A effort make tagging and using OSM data easier; bridging different worlds together
Date: Wed, 11 Dec 2019 05:38:02 -0700 (MST)

Hi all,

What could be the user interface for such a collection of rules?
I can think of a preprocessor like osmfilter or some kind of wiki tool which
could add hints to wiki pages.
Or maybe a rule generator which could create rules for a target program like
mkgmap?

Gerd



--
Sent from: 
http://gis.19327.n8.nabble.com/Developer-Discussion-f5233107.html


_______________________________________________
dev mailing list
dev@openstreetmap.org

https://lists.openstreetmap.org/listinfo/dev

_______________________________________________
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Reply via email to