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

Support for langRange facet #6

Open
wants to merge 5 commits into
base: maven
Choose a base branch
from

Conversation

sesuncedu
Copy link

White space makes the diffs look bigger than they really are.

DataTypeReasonerImpl changes are all on or around getDataRange.

RestrictedTextDataType changes are concentrated in applying facet, contains, and intersect, plus an extra constructor parameter and field.

git diff -w shows the changes properly

Adds dependency on google guava
RDF 1.1 gets rid of "plain literals", and instead defines "simple literals".
These have the same lexical form as "plain literals", but are defined as syntactic sugar for either xsd:string or rdf:langString, which partition the value space of PlainLiteral based on the absence or presence of a language tag.

rdf:langString is not used as an explicit datatype in rdf serializations (just like PlainLiteral).   It can appear as the range of a datatype.

The OWL 2 and RDF 1.1 specifications are not currently aligned (e.g. explicit xsd:string  types may be discarded by RDF processors).  The rdf:langRange facet is currently only formally defined for rdf:PlainLiteral, as previously this was the only datatype which could have a language range.

Since rdf:langString can be defined as a PlainLiteral with a langRange restriction of "*", I am allowing this facet to also be used on rdf:langString.
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