Re: RDF representation for pending terms

Hi Thomas,

thanks a lot for your reply.


>
> You can download raw RDF data of schema.org <http://schema.org> at 
> http://schema.org/docs/developers.html#defs, without the need to parse 
> the source RDFa file.
I had missed that. Great to know!

> That would be an abuse of the semantic of "rangeIncludes". 
> "rangeIncludes" typically means "the range of that property _includes_ 
> this class but the values of that propery might well be instances of 
> other classes", while rdfs:range means "all the values of that 
> property, all the time and everywhere, can be considered instances of 
> this class". Which is totally different when it comes to OWL reasoning.
>
I see your point in talking about abuse, however those could be viewed 
as additional restrictions, that one might want to use in a particular 
context/data set. Formally (and in practice too), the data modelled this 
way, and exported later, would still be compatible/interoperable with 
the initial schema (since the latter is more generic and, OWL-wise, 
doesn't actually say anything). I see it like inheritance in OOP: as 
long as you extend the same classes/interfaces and don't violate the 
contracts about their expected behaviours, specific extensions are still 
compatible with any software using those classes/interfaces. Even more 
so, if this is done with what you suggest about unionOf.

>       - Yes, I know there are cases like
>     http://schema.org/acceptsReservations
>     <http://schema.org/acceptsReservations>, those would need to be
>     dealt with manually and I just hope they're not so many (and I
>     hope I'm not too optimistic :-) ).
>
>     - I'd like to use a few pending definitions (eg,
>     http://pending.schema.org/InvestmentFund
>     <http://pending.schema.org/InvestmentFund>). Are these already
>     represented in RDF/RDFa somewhere? Like in GitHub?
>
>
> You can download the RDF data for the pending section from the link above.
>
Thanks for that too!

Marco

-- 

=========================================================================
Marco Brandizi <marco.brandizi@gmail.com>
http://www.marcobrandizi.info