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.

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

US versus British spellings #250

Open
brandonnodnarb opened this issue May 31, 2021 · 8 comments
Open

US versus British spellings #250

brandonnodnarb opened this issue May 31, 2021 · 8 comments
Milestone

Comments

@brandonnodnarb
Copy link
Member

Example:
In Aluminum, Hematite and Sulfur are US spellings. I'm sure there are many others.

Shall we include British spellings?
If so, is adding another rdfs:label tag sufficient or are there other preferred methods (e.g. skos:altLabel, something else?)

@dr-shorthair
Copy link
Collaborator

You could just have multiple rdfs:label with language tags:

<http://sweetontology.net/matrMineral/Hematite>
    rdfs:label "Hematite"@en-US ;
    rdfs:label "Haematite"@en-GB ;
.

Else if we agree that US-English is the default/canonical English:

<http://sweetontology.net/matrMineral/Hematite>
    rdfs:label "Hematite"@en ;
    rdfs:label "Haematite"@en-GB ;
.

Else if we agree that US-English is the default/canonical language:

<http://sweetontology.net/matrMineral/Hematite>
    rdfs:label "Hematite" ;
    rdfs:label "Haematite"@en-GB ;
.

Else we could just agree to limit the labelling to US-English.

This is a business or policy decision.

@smrgeoinfo
Copy link
Collaborator

I'd suggest having only one rdfs:label-- it makes SPARQL queries that pull a label easier (no language filter), but having a language label is good. Some convention would be a good thing to avoid mix of all three ( rdfs:label "Hematite"; rdfs:label "Sulfur"@en ; rdfs:label "Aluminum"@en-us ).

Currently I can find 12818 language labels in SWEET, and they're all @en, so seems that current practice is to use @en with convention that default English dialect is US.

How about using skos:altLabel for @en-GB, or any other dialect/language synonyms.

@dr-shorthair
Copy link
Collaborator

dr-shorthair commented Jun 2, 2021

I think that would not strictly match the semantics of skos:altLabel as defined in the SKOS reference.
Language variants are supposed to use language tags.
altLabel is for other kinds of label variants.
If you want to retain a single rdfs:label and avoid language-tag messiness there (which I understand) then I think this pattern would be a better fit to SKOS:

<http://sweetontology.net/matrMineral/Hematite>
    rdfs:label "Hematite"@en ;
    skos:prefLabel "Hematite"@en-US ;
    skos:prefLabel "Haematite"@en-GB ;
.

or

<http://sweetontology.net/matrMineral/Hematite>
    rdfs:label "Hematite" ;
    skos:prefLabel "Hematite"@en-US ;
    skos:prefLabel "Haematite"@en-GB ;
.

@smrgeoinfo
Copy link
Collaborator

Makes sense. I like this one:

<http://sweetontology.net/matrMineral/Hematite>
    rdfs:label "Hematite"@en ;
    skos:prefLabel "Hematite"@en-US ;
    skos:prefLabel "Haematite"@en-GB ;
.

@nicholascar
Copy link
Collaborator

I recommend against the rdfs:label + skos:prefLabel pattern and recommend skos:prefLabel + skos:altLabel.

The reason for this is that some vocab systems prefer SKOS-labels only or treat pairs of rdfs:label & skos:prefLabel as duplicates for the semantics of how to relate them, and therefore which is the primary, are unclear. Within just SKOS, as a SKOS design goal, this is perfectly clear: if you wish US or other spelling to be primary, make that the prefLabel and all others altLabels.

A skos:prefLabel & skos:altLabel split for languages is not against the SKOS semantics, see SKOS Ref, Example 19

@graybeal
Copy link
Collaborator

graybeal commented Oct 21, 2021

I agree with @nicholascar. Not just because BioPortal would look for skos:prefLabel first and rdfs:label only if no prefLabel is offered, and uses skos:altLabel is used for synonyms. I would not recommend rdfs:label for synonyms because it is likely to be misconstrued given the availability of skos:prefLabel.

Unfortunately BioPortal would struggle with language tags but that is a defect in BioPortal. It's going to get fixed I am sure. So absolutely I would use language tags to indicate GB spellings where they exist. When there is the same spelling, I'd use skos:prefLabel with "@en" as the language tag, and when the spelling is different I'd have two prefLabels: one in en-US, one in en-GB. This makes it trivial to further internationalize the vocabulary with other languages later, and still present the preferred label in each language (and still search for synonyms in each language, or across languages).

@rrovetto
Copy link
Collaborator

rrovetto commented Nov 8, 2021

I recommend allowing a flexible approach whereby the user can chose either US or British spelling, both of which are presented to them as alternatives or synonymous (if actually synonymous). They can select their display label.

Likewise for other languages: a no-English speaker should see the synonym in their language and be able to select it as their display and preferred label.

@nicholascar
Copy link
Collaborator

@rrovetto that is the intended use of SKOS prefLabels with language tags and different version of a single language's language tags can be used, as per the en-US & un-GB examples above. System preferences should be used for particular displays, so a person may enter in an @en and an @it par of prefLabels and another user may set their system to preferential display Italian tags.

@brandonnodnarb brandonnodnarb added this to the 3.6.0 milestone Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants