openstreetmap / id-tagging-schema

🆔🏷 The presets and other tagging data used by the iD editor
ISC License
160 stars 164 forks source link

Merge `openstreetmap/id-tagging-schema` and `ideditor/schema-builder` repos #1294

Open tordans opened 4 months ago

tordans commented 4 months ago

This came up a few times in conversations, so lets track it as an issue:

I think we should merge the openstreetmap/id-tagging-schema and ideditor/schema-builder repos into one.

Why…

How… Its quite simple technically speaking. I found those blog post a great help:

k-yle commented 4 months ago

see also: https://github.com/ideditor/schema-builder/issues/35

matkoniecz commented 3 months ago

Do we know why this repositories were split?

1ec5 commented 3 months ago

name-suggestion-index also uses schema-builder. Not sure if combining it with id-tagging-schema would make anything harder – or easier.

bhousel commented 3 months ago

name-suggestion-index also uses schema-builder.

Are you sure? I don't think it does?

1ec5 commented 3 months ago

Oh, my bad, it’s actually using id-tagging-schema to generate the presets. All good then. 😅

tordans commented 3 months ago

Another though: We could also use this opportunity to rename the repo to something less iD specific since many editors use the presets here (Rapid, GoMap, SC to some extend AFAIK, MapComplete to some extend AFAIK, …)

Maybe just "tagging-schema"? Or "editor-tagging-schema" to not be too presumptuous.

matkoniecz commented 3 months ago

I think it is fine to say "StreetComplete uses iD presets" (and yes, it does in several places - especially in shops and things overlays and for object descriptions).

Note that describing it as more general will encourage people to ask for changes improving things in say StreetComplete but breaking iD. Now such changes can be easily rejected (or are not asked in the first place)

Also, deprecations like this will create general confusion and will make this specific tagging schema harder to uniquely identify.