Skip to content

How to deal with the unique language constraint? #52

@mielvds

Description

@mielvds

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions