Skip to content

Add footnote to lang strings in SIP spec #173

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

lucasotodegraeve
Copy link
Contributor

I changed the the maximum cardinality of lang strings to 1 for the descriptive metadata part of the SIP spec.

I interpret the notation of the cardinality 1..1 on a lang string as:

<dcterms:title xml:lang="nl">mijn titel</dcterms:title>
<dcterms:title xml:lang="fr">mon titre</dcterms:title>

Where "the same semantic thing" might appear multiple times in different languages.

However, having 0..* or 1..* doesn't make much sense for lang string:

<dcterms:alternative xml:lang="nl">mijn alternative titel</dcterms:alternative>
<dcterms:alternative xml:lang="fr">mon titre alternatif</dcterms:alternative>

<dcterms:alternative xml:lang="nl">een tweede alternative titel</dcterms:alternative>
<dcterms:alternative xml:lang="fr">un deuxième titre alternatif</dcterms:alternative>

There is no way to know which strings belong together semantically. Do you agree? Is the current notation for cardinality good as is? In the datamodels the notation is slightly different.

@lucasotodegraeve lucasotodegraeve requested a review from mielvds May 20, 2025 10:44
@lucasotodegraeve lucasotodegraeve force-pushed the limit-lang-string-cardinality branch from 633fec5 to 32baee6 Compare May 21, 2025 16:01
@lucasotodegraeve
Copy link
Contributor Author

As discussed, I've updated the cardinalities to be either 1..* or 0..* and include a reference to a footnote.

@lucasotodegraeve lucasotodegraeve changed the title Limit maximum cardinality of lang strings to 1 Add footnote to lang strings in SIP spec May 22, 2025
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.

1 participant