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

How to deal with the unique language constraint? #52

Open
mielvds opened this issue Feb 16, 2023 · 0 comments
Open

How to deal with the unique language constraint? #52

mielvds opened this issue Feb 16, 2023 · 0 comments

Comments

@mielvds
Copy link

mielvds commented Feb 16, 2023

An scenario we've recently encountered that we're not sure how to visualize in a specfication document: some properties can allow multiple times, but only if they differ in language. In SHACL, the datatype would be rdf:langString, the sh:uniqueLang would be true and the sh:maxCount would be absent.

I noticed this tooling outputs [0..*] with datatype TaalString, but I can't find anything about the language needing to be unique. Did you encounter this scenario before? How does the Generator deal with it? Any opninions on how to communicate it properly?

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