Re: [web-annotation] Definition of specific resources: @Type

let's take a practicle example from the real world .. inspired from 
the wikipedia example.

If an italian is comming to Vienna and orders a coffee, and the waiter
 is bringing an American coffee, this will results in an emberasing 
situation both for italian customer and waiter. 

In the most cases, though "a coffee" the italian means and expreso:
https://en.wikipedia.org/wiki/Espresso

 and being in Vienna the default coffee should be Melange:
https://en.wikipedia.org/wiki/List_of_coffee_drinks#Wiener_or_Viennese_melange

 And it is rather an exception for Europeans to drink Cafe Americano:
https://en.wikipedia.org/wiki/List_of_coffee_drinks#Caff.C3.A8_Americano

This is why I claim that the type of the coffe is a "must" both during
 the ordering process (creation time) and in the billing process 
(delivery time).

I also want to claim that this is the natural behaviour for any 
customer!
What I really don't understand, why are the Semantic Web people so 
keen to get rid of Semantics? (for me the type is the core of the 
semantic)

-- 
GitHub Notification of comment by gsergiu
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/137#issuecomment-173377003
 using your GitHub account

Received on Wednesday, 20 January 2016 22:06:33 UTC