Re: linking from resource -> container ..

>> > I agree that backlinking (linking from an LDPR to its LDPC) should be possible, ... 
>> Henry, when you say "its LDPC", which (of the potentially many LDPCs that may list an LDPR as a member) one do you have in mind?
>> 
>> I could read your statements to be very general, or to apply to a more restricted set of cases that is (to me at least) not fully articulated.
>> 
>> I hear "its" to be singular, but that might also be other than what you intend.
>> 
> 
> I tend to think of an LDPR as having only one LDPC: the one that created it.
> But the points I was making on backlinking would not be affected by the possiblity
> of an LDPR having more than one ldp:contains relationship back.

Henry,

I think I understand what you keep referring to 'backlinking' 
- but, it's not what I am after.

As you say above, you refer to linking from a LDPR 'back' to the LDPC it is contained in. Then John just pointed out that in his proposal that an LDPC might be 'aggregative' in character, and therefore an LDPR might be a member in more than one LDPC. 

Anyway. This link/links are NOT what I am considering. I am referring to links which resource can use to refer it's containers - i.e. a Networth can point to it's Assets and Liabilities containers. 

regards, 
Roger

> 
> Btw in N3 there is a syntax for reverse linking
> 
> If the LDPC one finds
> 
> <> ldp:contains <joe>
> 
> Then <joe> could contain in terms of backlink
> 
> <> is ldp:contains of <.>
> 
> which is equivalent of
> 
> <.> ldp:contains <> .
>  
> 
>> 
>> Best Regards, John
>> 
>> Voice US 845-435-9470  BluePages 
>> Tivoli OSLC Lead - Show me the Scenario 
>> 
> 
> Social Web Architect
> http://bblfish.net/
>