Re: ldp-ISSUE-15 (sharing binary resources and metadata): sharing binary resources and metadata [Linked Data Platform core]

On 10/4/12 5:59 PM, Wilde, Erik wrote:
> hello all.
>
> On 2012-10-04 12:39 , "James M Snell" <jasnell@gmail.com> wrote:
>> Within Atompub, the distinction between edit and edit-media was largely a
>> bit of a necessary hack given the lack of any kind of formal data model
>> around a resource and it's data model. Within ldp, there exists the
>> opportunity to tighten this up significantly by leveraging things like
>> "describedBy" and "describes". A resource and that resource's metadata
>> are essentially two distinct related resources (in fact, there can be a
>> one-to-many relationship between the two). These can, and should be
>> managed just as you would manage any other kind of resource relationship.
> well said, and i agree that relations between "media resources" and
> "description resources" should be represented and discoverable by standard
> mechanisms. and btw, 'decries' so far is just a proposal but from what
> i've seen nobody has objected, and all feedback i have received so far
> said that there should be an inverse of 'describedby'. so i am encouraging
> this group to have a look at
> http://tools.ietf.org/html/draft-wilde-describes-link-01 and provide
> feedback. if i don't get any pushback, i will submit this draft for expert
> review better sooner that later, so that proper linking between resources
> could be established based on existing standards, both for 'describedby'
> as well as for 'describes'.
>
> cheers,
>
> dret.
>
>
>
>
+1

Is there any chance of evolving:


    Resources on the Web can be identified by any (registered) URI scheme
    and can be represented by any (registered) media type.  In many
    cases, applications establish specific (i.e., typed) relations
    between the resources they are concerned with, which can either be
    under their control, or controlled by another authority.  A common
    usage pattern for associating resources is to have resources which
    are descriptions of other resources.  This specification registers
    the 'describes' link relation, which allows applications to represent
    the fact that one resource is a description of another resource.


To something along the following lines:

    The Web can enables *entities* to be *denoted* by any (registered) 
URI scheme.
    These entities can be represented by content associated with any 
(registered) media type.
    In many cases, applications establish specific (i.e., typed) relations
    between entities, which can either be under their control, or 
controlled by another authority.
    A common usage pattern for URI based denotations is to have them 
resolve to content that
    describe other entities.  This specification registers the 
'describes' link relation, which allows applications to represent
    the fact that one entity is a description of another entity. For 
example, a profile document that describes a person
    where both entities (document and person) are unambiguously denoted 
by any (registered) URI scheme.


Maybe this can be collectively massaged via a Wiki document.


-- 

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