[RCP-44] Metadata Internationalization and Locale#168
Draft
darnjo wants to merge 4 commits into
Draft
Conversation
darnjo
marked this pull request as draft
October 30, 2025 08:26
psftc
reviewed
Oct 30, 2025
|
|
||
| Supporting regional and international metadata allows systems to display localized names for RESO Data Dictionary elements, which are based on U.S. English, while preserving interoperability of standard data elements. | ||
|
|
||
| This RCP adds fields in the Model, Field, and Lookup resources that allow a collection of name/value pairs to be communicated and searched. It uses ISO standards for locales, which are common in internationalization (i18n) applications, making localization (i10n) much easier. |
Collaborator
There was a problem hiding this comment.
localization == L10n (l10n) not i10n
|
|
||
| This RCP adds fields in the Model, Field, and Lookup resources that allow a collection of name/value pairs to be communicated and searched. It uses ISO standards for locales, which are common in internationalization (i18n) applications, making localization (i10n) much easier. | ||
|
|
||
| A collection of `DisplayNames` was used rather than a map to support filtering with any/all queries in OData, providing a simpler and more dynamic interface for end users. Clients can request metadata display names in the locale(s) of their choosing without metadata introspection to determine whether they're supported or not. If not, then no value matching the requested locale will be returned. |
Collaborator
There was a problem hiding this comment.
Use present tense for the decision? eg.
"... of DisplayNames is used rather than..."
A second edit could be "... of DisplayNames is used to support filtering with any/all queries in OData. A map was considered and rejected since the collection provides a simpler and more dynamic interface for end users."
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #67.
VIEW SPECIFICATION