Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt

You folks who want an enriched semantic payload describing the
finer-grained aspects of different modes & causes of policy-driven blockage
need to come up with some detailed proposals, maybe a controlled vocabulary
too.

Also, it’s clear that this is entirely separate issue from the original
proposal, for a single HTTP status code saying “legal restrictions” with a
SHOULD saying “please explain in the response body”.  Neither need depend
on the other.  -T

On Thu, Jun 14, 2012 at 10:11 AM, Albert Lunde <atlunde@panix.com> wrote:

> Rather than having details of the policy/legal etc. restrictions in
> additional headers, would there be any merit in having a structured XML
> mime multi-part, containing information in a parseable form?
>
> I suppose if one put text or HTML body parts first, a simple-minded client
> would display that, but an advanced client could get more details.
>
>
>
>
>