Re: composition and aggregation

hello henry.

On 2013-01-29 15:48 , "Henry Story" <henry.story@bblfish.net> wrote:
>You are saying that you need two relation
>ldp:contains a rdf:Property;
>   rdfs:domain ldp:Container;
>   rdfs:comment """
>  deleting this relation requires deletion of the resource that is the
>object 
>  of this relation.
>  """
>ldp:link a rdf:Property;
>   rdfs:comment """
>  a relation to another resource, that like a symbolic link on a unix
>file system 
>  does not entail the deletion of the object of the relation if removed. "
> 
>Mind you that ldp:link is so general you may wonder why not just use the
>top level
>property of rdf. Is there anything special about this link property at
>all?

do i really need two relations? i think (but maybe i am thinking something
wrong here) i need just one relation ldp:Content, and it simply associates
content. there must be exactly one such triple in what i POST. depending
on the document i POST, i may choose to include the triples that are
associated with that content, or not. if i include the triples, then i am
"embedding", if i don't, then i am "linking". the server doesn't look or
care (what it does do, of course, is to validate that there must be
exactly one ldp:Content in the RDF i am POSTing). when a client GETs the
RDF, content is either embedded in the resource, or it's not, and the
rules of the ldp:Content link then say that a client can try to GET the
actual content from the linked URI.

cheers,

dret.

Received on Tuesday, 29 January 2013 15:10:47 UTC