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 356 - Declare DS namespaces even for BDS or just for custom schemas?
Summary: Declare DS namespaces even for BDS or just for custom schemas?
Status: RESOLVED FIXED
Alias: None
Product: P3P
Classification: Unclassified
Component: Converting the P3P data schema to XML Schema (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Giles Hogben
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 355
  Show dependency tree / graph
 
Reported: 2003-10-02 10:12 UTC by Giles Hogben
Modified: 2005-06-30 19:44 UTC (History)
0 users

See Also:

Attachments

Description Giles Hogben 2003-10-02 10:12:23 UTC 
Declare DS namespaces even for Base Data Schema or just for custom schemas? We 
are proposing to use a different schema than P3P (unless we simply include the 
BDS inside the P3P Schema). Otherwise it will be necessary to declare a new 
namespace every time you use a data element.
Comment 1 Rigo Wenning 2003-10-03 04:15:00 UTC 
I think, at least the Base Data Schema (BDS) should be part of P3P 1.1. 
Otherwise every implementation of P3P would have to support mixing of 
namespaces. This is too much of a burden. 

Also, the BDS defines the things that _every_ user agent has to understand. We 
would complicate this by doing things outside the P3P 1.1 Specification.