Re: Schema.org and OWL

Holger at TopBraid used to have an OWL version, http://topbraid.org/schema/
but they switched to using a SHACL representation instead.

While it would be nice if people using OWL tools could link or base their
terms on those in schema.org, I wouldn't waste a lot of time agonizing how
to express our loose domain/range construction in OWL-eze. OWL tools,
especially DL, tend to crash out easily when they run into unexpected
things.

The old schemaorg.owl file was a oneoff made in 2011, if I recall. But our
main definitions are essentially RDF/S. I'd look at SHACL (and ShEx; it is
a pity they diverged) if the goal is to characterize useful data shapes,
rather than just trying to attach properties to types. e.g.
http://book.validatingrdf.com

Dan

On Wed, 6 Jun 2018, 05:51 Thomas Francart, <thomas.francart@sparna.fr>
wrote:

> Richard
>
> Watch out for uppercase/lowercase :
>
> <owl:class> must be <owl:Class>
> <owl:unionof> must be <owl:unionOf>
> <owl:objectproperty> must be <owl:ObjectProperty>
> <owl:datatypeProperty> must be <owl:datatypeProperty> (only 2 of them ?
> exchangeRate and interactionCount - strange)
> namedindividual must be NamedIndividual
> rdf:description must be rdf:Description
> "rdf:Description rdf:resource=" must be "rdf:Description rdf:about="
>
>
> Why is "http://schema.org/DataType" subclassOf rdfs:Class ? It seems it
> should be somehow connected to schema:Boolean, etc, but it is not.
>
> <rdfs:subPropertyOf rdf:resource="rdfs:label"/> : you can't use a QNAME
> here, it must be the full URI of rdfs:label
>
> additionalType subPropertyOf rdf:type : looks surprising to me;
>
>
> <owl:ObjectProperty rdf:about="http://schema.org/repeatFrequency">
>         <rdfs:subPropertyOf rdf:resource="
> http://health-lifesci.schema.org/frequency"/> : SDO really have a
> property from the core defined as a subproperty from a property in an
> extension ?!
>
>
>
>
> 2018-06-06 14:05 GMT+02:00 Richard Wallis <richard.wallis@dataliberate.com
> >:
>
>> Calling folks with more OWL experience than me!
>>
>> The schema.org site has an OWL definition file that has not been
>> maintained since April 2014: http://schema.org/docs/schemaorg.owl. Also
>> the structure and syntax of the file needs some attention.
>>
>> To help with the occasional questions about accessing processable
>> representations of the vocabulary; to attempt to close an issue (#1611
>> <https://github.com/schemaorg/schemaorg/issues/1611>); and to help with
>> a personal project, I have had a look at producing an up to date, improved,
>> maintainable version of the file.
>>
>> My first attempt can be downloaded/viewed here:
>> https://s3.amazonaws.com/rjwPublicData/public/schemaorg.owl
>>
>> I am looking for comments, suggestions, and help around a few aspects of
>> this work in progress:
>>
>>    - Is it generally ‘a good owl file’
>>
>>    - Should it contain more/less info about the vocabulary and its terms
>>
>>    - Specifically with reference to domainIncludes and rangeInclude -
>>    mapped to rdfs:domain & rdfs:range with owl:unionOf collections:
>>
>>    - Is this the best/only way to represent multiple domain & ranges for
>>       an objectproperty?
>>
>> The only I know of, I would love to know alternatives.
>
>>
>>    -
>>       - Have I got the syntax correct?
>>
>>       - Several people use Protégé <https://protege.stanford.edu/> as a
>>    tool for this kind of effort - I am trying to identify what syntax, will
>>    enable this tool to recognise the multiple domain/ranges when importing
>>    this file.
>>
>>
> I can confirm that, after fixing the lowercase/uppercase error, the file
> can be opened in Protégé, with class Unions properly displayed.
>
>
>
>
>
> Best
> Thomas
>
>
>
>> If anyone out there with more OWL experience than me (not difficult),
>> could spend a few minutes taking a look at this and commenting, it would be
>> greatly appreciated.
>>
>> ~Richard
>>
>> Richard Wallis
>> Founder, Data Liberate
>> http://dataliberate.com
>> Linkedin: http://www.linkedin.com/in/richardwallis
>> Twitter: @rjw
>>
>
>
>
> --
>
> *Thomas Francart* -* SPARNA*
> Web de *données* | Architecture de l'*information* | Accès aux
> *connaissances*
> blog : blog.sparna.fr, site : sparna.fr, linkedin :
> fr.linkedin.com/in/thomasfrancart
> tel :  +33 (0)6.71.11.25.97, skype : francartthomas
>