Open tyrasd opened 2 years ago
The idea probably was in pursuit of a schema-agnostic iD. I don’t know if any forks are maintaining their own tagging schemas, but in principle a tasking manager could be set up to tailor the presets to a task-specific set or something. JOSM has this capability with swappable preset packs, but I’m not sure about the level of demand for iD to support something similar. I personally find this separate repository limiting, because we haven’t fully built out the meta-schema for id-tagging-schema yet – there are plenty of field types worth adding, for example.
(FWIW as an irregular contributor, I (also) have found it confusing which to find in in which repo)
Let's discuss the suggestion from https://github.com/ideditor/schema-builder/commit/d9c23fac2a3d1733e55c841c1e9e476ad78e2f7f#commitcomment-64100888:
Right out of the box, I would agree. I thought that there was a perhaps a reason for the repositories being structured like this. Perhaps some forks are using it to maintain their own set of presets?! Maybe @quincylvania could explain the original reasoning?