Re: additionalType property, vs extending Microdata syntax for multiple types

On 6/20/12 1:01 AM, Ivan Herman wrote:
> Dan,
>
> Using owl:equivalentProperty is a very strong statement. It does not only mean that, if I use schema:additionalType, this also means rdf:type, but it also means that anybody in the World may decide to use schema:additionalType anywhere where rdf:type is used even if, in fact, the data has nothing to do with schema.org. rdf:type being such a core property of the RDF world, even part of many syntaxes, I am not sure yet what consequences that would lead to.

Nothing harmful. The processors of this kind of relationship already 
understand what's entailed.
>
> I think I would prefer simply stating an rdf:subPropertyOf. It covers the schema.org use case, it is enough for RDF savy processors to generate the rdf:type statements and it does not do anything more.

But, I doubt the existence of RDF savvy processors that handle 
rdfs:subPropertyOf while not being able to handle 
owl:equivalentProperty. At the end of the day, isn't this all about 
creating a feature for processors that handle multiple vocabularies 
without disrupting pure microdata processors that don't care about 
fine-grained semantics of relationships?

>   Besides, while there might be many tools out there in the Linked Data space that do such basic RDFS reasoning already, the number of processors that understand the OWL terminology might be much less frequent.

In my experience rdfs:subPropertyOf and owl:equivalentProperty are 
typically supported re. basic reasoning by RDF processors that offer 
basic reasoning functionality .

>
> Another issue came up during the discussion, but is much more general. Ideally, it would be nice to get, via content negotiation, an RDF file at http://schema.org (in Turtle and/or RDF/XML) that would include this and other possible statements on the Schema Vocabulary. It would be helpful 'following your nose' for the vocabulary, RDFa processors may use it to expand on the schema terms, etc.

+1

Or, simply refer to said resource via <link/> in <head/> should content 
negotiation be problematic.

>   additionalType subProperty may then be part of that file, but, for example, similar statements could be added to bind the schema.org rNews terms to the non-schema versions (b.t.w., that may be a good use case for equivalentProperty), or if, at some point, there is a similar mapping of DC terms to schema.org.

+1

Kingsley
>
> Cheers
>
> Ivan
>
>
> On Jun 19, 2012, at 19:24 , Dan Brickley wrote:
>
>> Thanks everyone. Lots of mail!
>>
>> I have tried to make a brief summary of some of the points in the Web
>> Schemas wiki, just a sketch of individual positions really rather than
>> a summary of the whole debate. I also started there to write up
>> details of a concrete proposal for 'additionalType'.
>>
>> http://www.w3.org/wiki/WebSchemas/additionalTypeProposal ...
>>
>> Since nobody has volunteered to lead an effort to get Microdata syntax
>> changed to support multiple types from different vocabularies, and on
>> balance after reading thru all the debate, I think we should go for
>> the new property approach.
>>
>> I'd like to make sure that we capture all the concerns people have in
>> the Wiki and in the resulting property definition, and to give some
>> thought to how validators and checkers ought to behave.
>>
>> Peter, Egor, others, ... can you live with a new property here? (one
>> of 'additionalType' or 'type') Any preferences on name?
>>
>> cheers,
>>
>> Dan
>>
>
> ----
> Ivan Herman, W3C Semantic Web Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> FOAF: http://www.ivan-herman.net/foaf.rdf
>
>
>
>
>
>
>
>


-- 

Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen