- From: Arnaud Le Hors <lehors@us.ibm.com>
- Date: Thu, 13 Jun 2013 09:00:15 -0700
- To: Henry Story <henry.story@bblfish.net>
- Cc: public-ldp-wg@w3.org
- Message-ID: <OFC4457D0D.C0376A27-ON88257B89.00575C99-88257B89.0057E9DA@us.ibm.com>
Henry Story <henry.story@bblfish.net> wrote on 06/13/2013 08:44:07 AM: > That is we can describe resources as being of certain types, and that > they allow certain types of interactions. We can declaratively describe > a resource as allowing certain actions. By doing that of course we > describe the web agent that the server we are interacting with is. > But we did not need to describe the web agent in full to do this, just > the resources we are interested in. We're mincing words here. When the description of the resources implies a specific behavior from the agent we're effectively describing the agent too. But as I said before I know you think the interaction is an integral part of the resource type and therefore the mere indication of the resource type in RDF is all one needs. We've heard others saying they don't see it that way though. Rather than continuing to argue over who's right I'm proposing we accept that there are two ways to look at this and accommodate both ways. This may be seen as introducing some redundancy but that's often how we get something that works for everyone in the standards world. -- Arnaud Le Hors - Software Standards Architect - IBM Software Group
Received on Thursday, 13 June 2013 16:02:38 UTC