Re: ldp-ISSUE-38 (filtering, inlining): filtered representations and inlining [Linked Data Platform core]

On 11/19/12 5:14 PM, Wilde, Erik wrote:
> hello roger.
>
> On 2012-11-19 13:49 , "Roger Menday" <Roger.Menday@uk.fujitsu.com> wrote:
>>> On 2012-11-19 09:19 , "Roger Menday" <roger.menday@uk.fujitsu.com> wrote:
>>>> This specific issue wasn't about the 'storing' (the 'write') part.
>>>> I was specifically concerned with the reading part.
>>> given that LDP is a service and a service should only expose its service
>>> surface, you cannot make any assumptions that you reach deeply into some
>>> back-end storage. all you can interact with are LDP concepts, unless the
>>> service exposes additional affordances that give you more interaction
>>> capabilities.
>> Did I say something to suggest otherwise .. ?
>> I'm definitely *not* making assumptions about the back-end, only that it
>> can get exposed as a Graph. That's it.
> that already is an assumption, isn't it?

It isn't an assumption. More like a fact, since LDP is supposed to be 
based on RDF -- an entity relationship model endowed with explicit 
entity relationship semantics, expressible as an entity relationship 
graph? This can all happen on :

1. paper
2. on a computer --  using a variety of markup syntaxes
3. on a local area network using hyperlinks that resolve locally -- ditto
4. on a wide area network (e.g. Web or Internet) where hyperlinks are 
either HTTP URIs or de-referencable URIs (i.e., that might not be http: 
scheme based) -- ditto.


[SNIP]

-- 

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