Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should Description extends InternationalString? #78

Open
desruisseaux opened this issue Dec 1, 2022 · 0 comments
Open

Should Description extends InternationalString? #78

desruisseaux opened this issue Dec 1, 2022 · 0 comments
Milestone
3.1

Comments

@desruisseaux
Copy link
Contributor

ISO 19157 defines an DQM_Description object with only two properties:

  • textDescription: a mandatory character sequence.
  • extendedDescription: an optional BrowseGraphic.

Having Description as a type distinct from InternationalString is a minor complication for defining a unified parameter API (#74). It is also a complication for users by adding an indirection level in the majority of cases where they only want the text description. Description may be easier to use if the textDescription property is removed and replaced by inheritance. In other words, Description would be considered as a character sequence with an additional property, which is an optional illustration.
@desruisseaux desruisseaux added this to the 3.1 milestone Dec 1, 2022
desruisseaux added a commit that referenced this issue Dec 1, 2022
@desruisseaux
Document better the mapping of DQM_Description to unified parameter…
de5cc61 
… API.

Related to #78 but not yet a resolution
(whether `Description` should extend `InternationalString` is still an open question).
@desruisseaux desruisseaux mentioned this issue Dec 1, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
3.1
Development

No branches or pull requests
1 participant
@desruisseaux