- From: Carlos Iglesias <carlos.iglesias@fundacionctic.org>
- Date: Mon, 26 Sep 2005 10:47:10 +0200
- To: "Charles McCathieNevile" <chaals@opera.com>, <public-wai-ert@w3.org>
> Are we going to follow this up with the HTML group? > > cheers > > Chaals > I think we really should, but I don't like the current P3P aproach at all. IMO if the link element is going to be used with the EARL reports there are several conditions we should observe, ideally: - The relationship type should be clear established: accessibility, privacy, etc. - The relationship role should be clear established too: conformance, preferences, etc. - The format need to be known: p3p, earl, etc. - The format version need to be known too: 1.0, 1.1, 2.0, etc. This way user agents could know all the necessary about the linked document without the necessity of explore the document itself. And this is why I don't like to adopt the current P3P approach: <link rel="earlv1" href="http://www.wats.ca/w3c/earl_report.rdf" /> IMO again this is a bad use of the rel attribute because it should describe relationships and I think that earlv1 is not a relationship at all, it's a format. In addition, what happens when the earl become updated with a v2? So, I would prefer something like: <link rel="accessibility" role="conformance" type="application/earlv1" href="www.example.com/earlreport.rdf" title="EARL accessibility report" /> I think this approach fulfils the previous desired conditions and is more flexible, allowing things like: <link rel="accessibility" role="information" type="text/html" href="www.example.com/accessibility.html" title="Information about the accessibility applied in this site" /> <link rel="mobile" role="conformance" type="application/earlv1" href="www.example.com/earlreport.rdf" title="EARL mobileOK conformance report" /> Waiting for your thoughts... Regards, CI. > ------- Forwarded message ------- > From: "Shadi Abou-Zahra" <shadi@w3.org> > To: "John Foliot - WATS.ca" <foliot@wats.ca> > Cc: www-html-editor@w3.org, public-wai-ert@w3.org > Subject: Re: [Moderator Action] Comment: 23. XHTML > Metainformation Attributes Module > Date: Tue, 07 Jun 2005 14:26:19 +0200 > > > Hi John, > > > John Foliot - WATS.ca wrote: > > The current XHTML 2 draft has expanded and added to the predefined > > list of relative values > > > (http://www.w3.org/TR/xhtml2/mod-metaAttributes.html#col_Metai > nformation): > > Example: <link rel="P3Pv1" href="http://www.wats.ca/w3c/p3p.xml" /> > > (I'm glad you caught this one... I had wondered about it before). > > May I suggest that another value be added to the newly > expanded list, > > that of EARL: > > ************* > > earlv1 > > Refers to an EARL Report Reference File. See [EARL - > > > http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Requirements-20050615.html]. > > Example: <link rel="earlv1" > > href="http://www.wats.ca/w3c/earl_report.xml" /> > > or: > > <link rel="earlv1" > href="http://www.wats.ca/w3c/earl_report.rdf" > > /> > > *************
Received on Monday, 26 September 2005 08:49:01 UTC