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

Connection of DocumentService and Offer #9

Open
cKlee opened this issue Dec 18, 2013 · 1 comment
Open

Connection of DocumentService and Offer #9

cKlee opened this issue Dec 18, 2013 · 1 comment

Comments

@cKlee
Copy link
Member

cKlee commented Dec 18, 2013

This might be expressed this way:

dso:DocumentService a owl:Class ;
    rdfs:subClassOf [
        a owl:Restriction ;
        owl:onProperty daia:availableOf ;
        owl:allValuesFrom schema:Offer
    ] .

Meaning:All instances of DocumentService that have the property daia:availableOf or is connected through the inverse property daia:availableFor are also instances of the class schema:Offer.

This explicitly says that

$item daia:availableFor $interloan .
$interloan a dso:Interloan.
] .

$interloan is an instance of class schema:Offer.

@dini-ag-kim/bestandsdaten

@nichtich
Copy link
Member

We could simply define daia:availableFor to imply a schema:Offer: gbv/daia-rdf#1

I strongly dislike any constructs in ontologies that make use of blank nodes.

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

2 participants