Skip to content

Docs: Clarify referencing for name#149

Closed
tordans wants to merge 1 commit intoideditor:mainfrom
tordans:patch-10
Closed

Docs: Clarify referencing for name#149
tordans wants to merge 1 commit intoideditor:mainfrom
tordans:patch-10

Conversation

@tordans
Copy link
Copy Markdown
Collaborator

@tordans tordans commented Apr 28, 2024

I think this wording should be like in this PR, right?

However, I am not sure if this whole part is actually true. does adding a reference for the name really mean that also terms and aliases are copied? Is there a way around this, like adding terms (or an empty array) in the present itself?

Or could it be that one has to reference the preset for each of those keys separately?

A preset can optionally reference the label of another by using that preset's name contained in brackets, like {preset}. In which case the presets's terms and aliases are also automatically sourced from that other field. This is for example useful for regional presets which should get the same labels as the preset they are based on.

@tordans
Copy link
Copy Markdown
Collaborator Author

tordans commented Apr 28, 2024

There is another question here on how to best explain the underscore case for all those places where we explain referencing of keys, which is at least 3 places in the readme. See #148 for why…

@tordans tordans changed the title Readme: Clarify referencing for name Docs: Clarify referencing for name Mar 6, 2025
Comment thread README.md
Upon merging into the `main` branch, this is sent to Transifex for translating to other localizations. Changing the name of an existing preset will require it to be re-translated to all localizations.

A preset can optionally reference the label of another by using that preset's name contained in brackets, like `{preset}`. In which case the presets's _terms_ and _aliases_ are also automatically sourced from that other field. This is for example useful for regional presets which should get the same labels as the preset they are based on.
A preset can optionally reference the name of another by using that preset's name in brackets, like `{folder/preset}`. In which case the presets's _terms_ and _aliases_ are also automatically sourced from that other field. This is for example useful for regional presets which should get the same labels as the preset they are based on.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A preset can optionally reference the name of another by using that preset's name in brackets, like `{folder/preset}`. In which case the presets's _terms_ and _aliases_ are also automatically sourced from that other field. This is for example useful for regional presets which should get the same labels as the preset they are based on.
A preset can optionally reference the identifier of another by using that preset's name in brackets, like `{folder/preset}`. In which case the presets's _terms_ and _aliases_ are also automatically sourced from that other field. This is for example useful for regional presets which should get the same labels as the preset they are based on.

they are not referencing their name, from what I see

For example https://github.com/openstreetmap/id-tagging-schema/blob/5c85ba0b277f21739a58629aa29e2cea802dc655/data/presets/shop/art.json would be referenced by shop/art - not by Art Store

maybe "location" would also work?

matkoniecz added a commit to matkoniecz/schema-builder that referenced this pull request Jan 6, 2026
For example https://github.com/openstreetmap/id-tagging-schema/blob/5c85ba0b277f21739a58629aa29e2cea802dc655/data/presets/shop/art.json would be referenced by `shop/art` - not by `Art Store`

maybe "identifier" would also work?

this is alternative to and closes ideditor#149
@matkoniecz
Copy link
Copy Markdown
Contributor

#256 got extra improvements from @k-yle

@tordans tordans closed this in #256 Jan 11, 2026
@tordans tordans deleted the patch-10 branch January 11, 2026 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants