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

Multi-language support question #1

Open
dalito opened this issue Dec 7, 2022 · 2 comments
Open

Multi-language support question #1

dalito opened this issue Dec 7, 2022 · 2 comments

Comments

@dalito
Copy link
Contributor

dalito commented Dec 7, 2022

When I try with a concept table such as (template version 0.4.3)

Concept IRI*	Preferred Label*	Preferred Label Lang code	Definition*	Definition Language Code
ex:test/term1	term1	en	def for term1	en
ex:test/term1	Begr1	de	Def für Begr1	de

the result is

VIOLATION: Validation Result in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent):
        Severity: sh:Violation
        Source Shape: <nfd3f058c64984a7d8df8ee78c1d1bfc8b79>
        Focus Node: <http://example.org/test/term1>
        Value Node: <>
        Message: More than 1 values on <http://example.org/test/term1>->skos:definition

The file you supplied is not valid according to the vocpub profile.

It seems that it is necessary (with the vocpub-profile) to give each translation of a concept its own IRI. This seem more SKOS-XL-like but how would one generate (from SKOS reference):

<MyResource>
  skos:prefLabel "animals"@en ;
  skos:altLabel "fauna"@en ;
  skos:hiddenLabel "aminals"@en ;
  skos:prefLabel "animaux"@fr ;
  skos:altLabel "faune"@fr .

with vocexcel?

@dalito
Copy link
Contributor Author

dalito commented Dec 7, 2022

I just had a look at the vocpub-profile. The unique language is specified here if I understand correctly.

In contrast, the textual description for requirement 2.3.1a of the profile makes no claim about concept labels in differrent languages.

@dalito
Copy link
Contributor Author

dalito commented Dec 14, 2022

What I speculated was not the true reason. Using sh:uniqueLang is not restricting labels to one language but prevents more than one label per language. The (unintended?) restriction to one language comes from sh:maxCount 1 (Requirement-2.3.1b). If this constraint is removed, vocexcel will generate SKOS-files with multiple languages.

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

No branches or pull requests

1 participant