This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 168 - consider adding human-readable explanation strings to all elements that don't have them
Summary: consider adding human-readable explanation strings to all elements that don't...
Status: RESOLVED WONTFIX
Alias: None
Product: P3P
Classification: Unclassified
Component: Vocabulary extensions (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: P3P1.1
Assignee: Lorrie Cranor
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-10 21:32 UTC by Lorrie Cranor
Modified: 2003-07-30 17:27 UTC (History)
0 users

See Also:


Attachments

Description Lorrie Cranor 2003-03-10 21:32:32 UTC
Some P3P elements have human-readable fields to provide further explanations, for 
example via LONG-DESCRIPTION. Consider adding these fields to all P3P elements 
that don't have them, or identify a set of elements to add them to.
Comment 1 Lorrie Cranor 2003-06-11 16:19:35 UTC
We have discussed this on two conference calls.  This could be done for a specific set of 
elements or generically.  It appears that the way the extension mechanism is defined in 
the P3P schema we cannot add such elements in arbitrary places -- for
example, I think we can add them to high-level elements such as
PURPOSE but not as sub-elements of individual PURPOSE elements. There is some 
interest in adding these elements selectively, but also concerns that sites will try to use 
them to gain more wiggle room. We agreed that we need to consider proposals on a 
case-by-case basis. Nobody has raised any specific proposals to date.

This  item will be closed in a few weeks unless someone comes forward with a specific 
proposal for us to consider.