[Planning] Major release version 7 with breaking changes

[tordans]

This issue is used to track the next major version of the schema which will have breaking changes. Part of this ticket is to track communicating the change to users of the tagging-schema data.

Planned breaking changes:
(Generally we first add support in iD, then merge the schema and use the new features in the tagging-schema (repo))

• allow more complex prerequisiteTags for fields #137 @k-yle
  • schema-builder: allow multiple prerequisiteTags #87
  • iD: support multiple prerequisiteTags for presets openstreetmap/iD#9511
  • tagging-schema: not required
• Delimited translated strings should be converted to arrays in dist output #84
  • schema-builder: store terms and aliases as an array in the translation files #227
  • iD: process terms and aliases as arrays openstreetmap/iD#11323
  • tagging-schema: not required
• Allow crossreferencing of labels between fields and presets #162
  • schema-builder: allow individual field options to reference other translations #230
  • iD: allow individual preset field options to reference other translations openstreetmap/iD#11325
  • tagging-schema: not required
• Allow referencing the locationSet.exclude #151
  • schema-builder: allow fields & presets to reference the locationSet from other files #226
  • iD: not required
  • tagging-schema: not required
• Validator: lanes tagging by using numeric values only openstreetmap/iD#8607
  • schema-builder: add integer field type #217
  • iD: support integer preset fields openstreetmap/iD#11181
  • tagging-schema: not required

Not breaking but might require UI updates:

• Add measurement field type #15
  • schema-builder: Implement a schema for the measurement field #198
  • iD:
  • tagging-schema:
• Add field type for fields that accept opening_hours syntax #100 @k-yle
  • schema-builder: Add schedule field type #101
  • iD: Add YoHours button to recurring schedule fields openstreetmap/iD#9678
  • tagging-schema: change opening_hours-like fields to type=schedule openstreetmap/id-tagging-schema#1537

Not breaking but bigger change:

• Presets should enumerate expected roles #134 @k-yle
  • schema-builder: define a schema for relation members #174
  • iD: not required
  • tagging-schema: add definitions for the structure of 31 relation presets openstreetmap/id-tagging-schema#1538

Communication:

• Ping users from https://github.com/openstreetmap/id-tagging-schema/wiki/Projects-that-are-using-this-tagging-schema – consumers should pull version 6 (eg from npm) and not master
• Prepare the changelog for those changes

out-of-date notes (click to expand)

Issues that we might look at in detail for this next major release

https://github.com/ideditor/schema-builder/issues/137
https://github.com/ideditor/schema-builder/issues/25
https://github.com/ideditor/schema-builder/issues/180
https://github.com/ideditor/schema-builder/issues/150
https://github.com/ideditor/schema-builder/issues/141
https://github.com/ideditor/schema-builder/issues/85

[tordans]

@Zverik, @bryceco, @pietervdvn, @mvexel, @Bonkles, @westnordost, @simonpoole FYI this issue is tracking the next major release of the id-tagging-schema which will have breaking changes and some things that you might want to update in your UIs.

[pietervdvn]

Thanks for the heads up! I'll be tracking this here in our issue tracker.

MapComplete has a script to convert id-schema items into mapComplete-schema; the output is committed into our repository. In other words, nothing will break at our side when the upgrade is done, but updating won't be possible until I manually run this process. I also don't expect too much problems upgrading the relevant script (but that'll have to wait, as I'm quite busy right now).