Re: ldp-ISSUE-92 (interaction model): Change rel=type to rel=profile for client introspection of interaction model [Linked Data Platform Spec]

> 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>?

> >> By Alexandre's own example (making a backup of an LDPC/LDPR), the
> >> backup is just a document (it has the same RDF content, including 
> >> the same rdf:type(s), but a different interaction model), not an LDPC 
or LDPR.
> If you copied the graph, would you not have the URLs pointing to the
> original URL?

Right.  The triples in my head were different (but mine were incorrect).

> I suppose the issue is to do with moving without resolving the 
> graph, which seems like of course very prone to 
> creating bad errors.

Right.  And if you don't resolve the URIs in the graph, it's probably true 
that you don't have an RDF graph (although I haven't checked the formal 
definition), you have a representation that *could be converted into an 
RDF graph* if given a base URI.  I'm not interested in breaking new ground 
on how to do that movement safely/sanely.

> profile seems more specific. 

More specific (than type) could be good or bad in your view, I'm not sure 
which. 
As I related on a call, I did consult with the RFC author first and he 
thought profile was a reasonable fit for our use case.  To paraphrase him, 
profile is intended as a lightweight way to refine the definition of 
existing media type(s) when you don't want to register a new media type. 
As Alexandre has said, defining a new media type would be the usual way to 
do what LDP is doing.

If I read "more specific" to mean "-1 that", do you feel that rel=type is 
The Right Choice (anything else -1), would you prefer we mint our own URI 
(which is completely allowed by 5988), or what?  Seems like in the ideal 
case we use the list to find apparent consensus and then vote on the call 
to confirm that.  Otherwise we'll be here until 10 minutes after the sun 
goes nova.


Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario