Re: comment on telconf 07-11-2012 : what is webid

On 11/9/12 8:14 PM, Jürgen Jakobitsch wrote:
> hi,
>
> just two small notes on today's telconf and the definition of what a
> webID is.
>
> 1. just to keep us out of troubles, i took a look around and found that
> the domain of predicate "denote" is widely used to be "URI" [1][2][3].
> none of the rare cases i found was something like "URL denote".

Yes, I reluctantly accept/accepted URL. URI abstraction is where the 
power lies. The name (denotation) of an entity has to be distinct from 
the location of its descriptor (description document). ODBC and JDBC 
have long demonstrated the power of name resolution based abstraction 
when applied to data access. You always have:

1. Data Source Name
2. Data Access Address in the form of a Connection String which where 
URLs come into play.

Saying: de-referencable URIs is really the way to go re. LinkedData, but 
we might have to leave people to understand this in their own time. 
These things have been raging for years now with little progress within 
W3C mailing lists and groups.

>
> 2. the "uniquely" thing.
> using IFPs requires knowledge about the property itself.

It requires access to an entity description and comprehension of entity 
relationship semantics. It's a nice exemplar, but tricky in the base 
definition as demonstrated by responses during yesterday's meeting.

>   is there any
> problem with that?
> an agent might (will in most cases) need to get the property's
> description also.
>
> wkr turnguard
>
> [1] http://dbooth.org/2010/ambiguity/paper.html
> [2] http://www.w3.org/wiki/SocialMeaning
> [3] http://bit.ly/YTdz3N (as i understand it)
>
>


-- 

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