hyperRDF

hi Kingsley, 

I still think that our RESTful protocol for robots shouldn't require the knowledge of types for it to operate correctly.
And I don't see this on the human Web either ... 

I believe that we are defining a kind of HTML-for-robots - in RDF. One of the important outcomes of the LDP activity is a vocabulary for doing something quite like <forms> for these robots. So hyperRDF is where (I hope) we will end up. I don't think that LDP 1.0 will cover all of it, but, I hope that we can eventually reach it with some future work. 

thanks, 
Roger


On 7 Jan 2014, at 20:29, Kingsley Idehen wrote:

> On 1/7/14 12:28 PM, Roger Menday wrote:
>>> On 7 Jan 2014, at 15:58, John Arwe <johnarwe@us.ibm.com> wrote:
>>> 
>>>>> If you have a graph that said
>>>>> 
>>>>>  <#joe> a :Elephant .
>>>>> 
>>>>> This would tell you quite a lot about how you can interact with <#joe> .
>>>> Ok, I'll bite.  What exactly does the rdf:type statement tell *code* about how it can interact with <#joe>?
>>> Say you have a robot that can walk around, and that knows that <#joe> is an elephant, then it will know a lot of things
>>> that are true of Elephants in general. IT will know that it has a trump, and that it walks around on 4 legs, that
>>> if it is older it has a certain size, etc... It will know that it eats, that is has good memory usually, etc. Those
>>> are all kinds of constraints on how the robot can interact with the elephant. For example it is quite different than how it
>>> would interact with <#jimmy> a cricket. With an elephant the human sized robot might have a chance to meet it head on.
>>> With a bacteria a cricket it might have to look in completely different places.
>>> 
>> 
>> Like on the web, I think that the robot will be offered interaction possibilities in the form of <forms> and this is how it makes it's way around.
>> 
>> Roger
> 
> No, because RDF is basically a language (i.e., a system of signs [for denotation], syntax [subject, predicate, object roles], relation semantics, and statements [subject->predicate->object triples]) that enables encoding and decoding of information.
> 
> As Henry just stated: it isn't about syntax. It isn't about media types. It's about language, one that usable like any other computer language, but modulo the historic deficiencies associated with data definition, representation, and access.
> 
> If RDF had stood for "Relations Definition Framework" instead of "Resource Description Framework" we would have saved ourselves something in the region of 13+ years of distracting debates in regards to how the World Wide Web's basic architecture enables a variety of abstractions layers atop the internet:
> 
> 1. document network (cloud)
> 2. data network (cloud)
> 3. semantically enhanced data network (cloud).
> 
> Links:
> 
> [1] http://bit.ly/JVkgP8 -- my Glossary of Terms (the kind of thing that RDF makes possible since I wrote this all up by hand using Turtle).
> 
> 
> Kingsley
>> 
>> 
>> 
>> ______________________________________________________________________
>>                                           Fujitsu Laboratories of Europe Limited
>>  Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE
>>  Registered No. 4153469
>>    This e-mail and any attachments are for the sole use of addressee(s) and
>>  may contain information which is privileged and confidential. Unauthorised
>>  use or copying for disclosure is strictly prohibited. The fact that this
>>  e-mail has been scanned by Trendmicro Interscan does not guarantee that
>>  it has not been intercepted or amended nor that it is virus-free.
>> 
>> 
>> 
> 
> 
> -- 
> 
> Regards,
> 
> Kingsley Idehen	
> Founder & CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter Profile: https://twitter.com/kidehen
> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
> 
> 
> 
> 
>