Re: rel="meta" or rel="acl" ? was: Web Access Cntrl Spec?

On 8/10/13 4:21 PM, Melvin Carvalho wrote:
>
>
>
> On 10 August 2013 10:56, Henry Story <henry.story@bblfish.net 
> <mailto:henry.story@bblfish.net>> wrote:
>
>
>     On 10 Aug 2013, at 00:18, Kingsley Idehen <kidehen@openlinksw.com
>     <mailto:kidehen@openlinksw.com>> wrote:
>
>     >> When talking about this with Alexandre Bertails he thought that
>     rel="meta" was
>     >> not the right relation and that rel="acl" would be more correct.
>     >
>     > Yes.
>     >
>     > It will be fixed.
>
>     We need to get those who have implementations to agree on this
>     first. :-)
>
>     And I am not sure what forum is available where we can agree on
>     edits to
>     the acl ontolgy or the http://www.w3.org/wiki/WebAccessControl
>     wiki page,
>     so I am sending this mail a bit widely around. The
>     WebAccessControl wiki
>     page suggests that the RWW Community Group is the place to discuss
>     this.
>
>     I suppose for the moment the WebAccessControl wiki page plays the
>     role of a
>     spec. It says:
>
>     [[
>       The client follows, for example, an HTTP header field:
>
>       Link: <meta/profile.meta>; rel=meta
>     ]]
>
>     Alexandre Bertails once argued that meta is too general, and that
>     this should
>     be an "acl" link. Neither "acl" nor "meta" are registered in the
>     iana document
>     http://www.iana.org/assignments/link-relations/link-relations.xhtml
>     which is I think where this needs to be registered.
>     See http://tools.ietf.org/html/rfc5988#section-6.1
>
>     For us to register this we should probably have something a bit more
>     spec like than the wiki page.
>
>     I also would like to add to the ontology
>      - support for regular expressions on urls
>      - a acl:include relation to include acls from other documents
>
>
> FYI: some comments from Timbl on #dig
>
> <timbl> I think rel=meta is a better choice
> <timbl> because we have running code which picks it up
> <timbl> and fragmenting the market does less damage.
> <timbl> I can see also an ACL file having other stuff (like ownership, 
> provenance, licence etc) and my gut feeling is that one flexible bag 
> is better than trying to defined lots of rigid bags and al algorithm 
> for what triples go in what.
>
> http://dig.csail.mit.edu/irc/dig/2013-08-10#T20-19-21
>
>
>
>     Social Web Architect
>     http://bblfish.net/
>
>
>
Meaning the same sentiment expressed in my prior post. We need to 
harmonize the many relations that address this matter.

We have an adopted relation for metadata (i.e. "meta") that doesn't seem 
to have an actual de-referencable URI, so that its description is 
machine-readable.

  Also explained in Turtle (updated to reflect the the 
<http://www.w3.org/1999/xhtml/vocab#meta> URI for meta), for additional 
clarity:

## Turtle based Description of how things look right now ##

<http://www.w3.org/ns/auth/acl#accessControl>
<http://www.w3.org/2000/01/rdf-schema#label> "acl" ;
<http://www.w3.org/2000/01/rdf-schema#domain> 
<http://xmlns.com/foaf/0.1/Document> ;
<http://www.w3.org/2000/01/rdf-schema#range> 
<http://xmlns.com/foaf/0.1/Document> ;
<http://www.w3.org/2000/01/rdf-schema#subPropertyOf> 
<http://www.w3.org/1999/xhtml/vocab#meta>,
<http://www.w3.org/1999/xhtml/vocab#lrdd>,
<http://www.w3.org/1999/xhtml/vocab#describedby>,
<http://www.w3.org/2007/05/powder-s#describedby> ;
<http://www.w3.org/2000/01/rdf-schema#comment> """ Associates a Web 
document with another document that describes its access control rules"""  .

<http://www.w3.org/1999/xhtml/vocab#describedby>
<http://www.w3.org/2000/01/rdf-schema#label> "describedby" ;
<http://www.w3.org/2002/07/owl#equivalenProperty> 
<http://www.w3.org/2007/05/powder-s#describedby>,
<http://www.w3.org/1999/xhtml/vocab#lrdd>,
<http://www.w3.org/1999/xhtml/vocab#meta>;
<http://www.w3.org/2000/01/rdf-schema#domain> 
<http://xmlns.com/foaf/0.1/Document> ;
<http://www.w3.org/2000/01/rdf-schema#range> 
<http://xmlns.com/foaf/0.1/Document> ;
<http://www.w3.org/2000/01/rdf-schema#seeAlso> 
<http://www.iana.org/assignments/link-relations/link-relations.xhtml> ;
<http://www.w3.org/2000/01/rdf-schema#comment> """Refers to a resource 
providing information about the link's context.""" .

<http://www.w3.org/1999/xhtml/vocab#lrdd>
<http://www.w3.org/2000/01/rdf-schema#label> "lrdd" ;
<http://www.w3.org/2000/01/rdf-schema#domain> 
<http://xmlns.com/foaf/0.1/Document> ;
<http://www.w3.org/2000/01/rdf-schema#range> 
<http://xmlns.com/foaf/0.1/Document> ;
<http://www.w3.org/2002/07/owl#equivalenProperty> 
<http://www.w3.org/2007/05/powder-s#describedby>,
<http://www.w3.org/1999/xhtml/vocab#describedby>,
<http://www.w3.org/1999/xhtml/vocab#meta>;
<http://www.w3.org/2000/01/rdf-schema#seeAlso> 
<http://www.iana.org/assignments/link-relations/link-relations.xhtml> ;
<http://www.w3.org/2000/01/rdf-schema#comment> """Refers to further 
information about the link's context, expressed as a LRDD ("Link-based 
Resource Descriptor Document") resource. See [RFC6415] for information 
about processing this relation type in host-meta documents. When used 
elsewhere, it refers to additional links and other metadata. Multiple 
instances indicate additional LRDD resources. LRDD resources MUST have 
an "application/xrd+xml" representation, and MAY have others.""" .


<http://www.w3.org/1999/xhtml/vocab#meta>
<http://www.w3.org/2000/01/rdf-schema#label> "meta" ;
<http://www.w3.org/2002/07/owl#equivalenProperty> 
<http://www.w3.org/2007/05/powder-s#describedby>,
<http://www.w3.org/1999/xhtml/vocab#lrdd>,
<http://www.w3.org/1999/xhtml/vocab#describedby> ;
<http://www.w3.org/2000/01/rdf-schema#domain> 
<http://xmlns.com/foaf/0.1/Document> ;
<http://www.w3.org/2000/01/rdf-schema#range> 
<http://xmlns.com/foaf/0.1/Document> ;
<http://www.w3.org/2000/01/rdf-schema#seeAlso> 
<http://www.iana.org/assignments/link-relations/link-relations.xhtml> ;
<http://www.w3.org/2000/01/rdf-schema#comment> """Widely used, but 
unregistered in IANA, and also lacks a Linked Data URI that resolves to 
a machine-readable description.""" .

## End ##


Links:

1. http://tools.ietf.org/html/rfc5988 -- current list of IANA registered 
relations
2. http://www.iana.org/assignments/link-relations/link-relations.xhtml 
-- actual IANA registration page
3. 
http://kingsley.idehen.net/DAV/home/kidehen/Public/Linked%20Data%20Documents/meta-data-relations-map.txt 

4. http://bit.ly/19jqx2P -- document presented via HTML based Linked 
Data browser (URIBurner instance)
5. http://bit.ly/13rd80y -- ditto via my Personal Data Space instance
6. http://bit.ly/19jr0Sy -- ditto via my RWW.IO hosted Personal Data 
Space instance .

-- 

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