W3C home > Mailing lists > Public > public-ldp-wg@w3.org > January 2015

Re: AC feedback on Proposed Rec

From: Steve Speicher <sspeiche@gmail.com>
Date: Mon, 26 Jan 2015 11:57:25 -0500
Message-ID: <CAOUJ7JpY-1G7gZQyD=iqw=smaeiN8r+es63HmL39-Pm9-rHf9Q@mail.gmail.com>
To: "Eric Prud'hommeaux" <eric@w3.org>
Cc: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
On Mon, Jan 26, 2015 at 9:59 AM, Eric Prud'hommeaux <eric@w3.org> wrote:
> Two AC reps voted proposed changes which we should address before writing
a transition req to REC per
> [[
> Minor (and maybe its just me), but this sentence is awkward to read:
> 9. Security Considerations
> ... "In cases where authentication is provided fails to meet the
requirements of a particular access control policy, the 403 status code
(Forbidden) can be sent back to the client to indicate this failure to meet
the access control policy."
> I think would read better as:
> "In cases where the provided authentication fails to meet the
> ]]

Accepted the change as recommended.

WG Resolution: http://www.w3.org/2013/meeting/ldp/2015-01-26#resolution_2
Changeset: https://dvcs.w3.org/hg/ldpwg/rev/ae4acedaf21b

> [[
> Great work!
> Not sure if it's a misunderstanding of mine or a typo but in example 4, 6
and 16 I would replace "http://www.w3.org/ns/ldp#RDFSource" by "
> If it is a misunderstanding it could be worth making it clear why the
usage of the more general class is preferred to using the more specific
type of the container.
> ]]

To help with understanding the setup examples and then the subsequent ones
that cover how containers are applied, I moved the last sentence before the
example to its own paragraph and expanded on the explanation of the
following examples.

WG Resolution: http://www.w3.org/2013/meeting/ldp/2015-01-26#resolution_3
Changeset: https://dvcs.w3.org/hg/ldpwg/rev/859f98c26867

Steve Speicher

> --
> -ericP
> office: +1.617.599.3509
> mobile: +
> (eric@w3.org)
> Feel free to forward this message to any list for any purpose other than
> email address distribution.
> There are subtle nuances encoded in font variation and clever layout
> which can only be seen by printing this message on high-clay paper.
Received on Monday, 26 January 2015 16:57:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:52 UTC