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 653 - art 10 jurisdiction issue
Summary: art 10 jurisdiction issue
Alias: None
Product: P3P
Classification: Unclassified
Component: Article 10 vocabulary issues (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Rigo Wenning
QA Contact:
Depends on:
Reported: 2004-04-05 20:35 UTC by Lorrie Cranor
Modified: 2004-04-26 18:04 UTC (History)
0 users

See Also:


Description Lorrie Cranor 2004-04-05 20:35:04 UTC
proposal is at
Comment 1 Lorrie Cranor 2004-04-12 20:11:30 UTC
resolved 4/7//04
Comment 2 Rigo Wenning 2004-04-20 13:54:51 UTC
This BNF is wrong as the Recipient has a different format for the comments.
In fact it is like <jurisdiction>PCDATA</jurisdiction> that most of the 
recipient subelements are made. I followed that and it should have the 
same expression power. But this has to go back to the WG for agreement.

  jurisdiction= "<JURISDICTION"
   " service=" quoted-URI
   [" short-description=" quotedstring]

Now it is like this
"&lt;jurisdiction [required]
    "service=" quoted-URI &gt;
		*recdescr                  |  ; legal entities in the jurisdiction 
"&lt;/jurisdiction&gt;                 |  ; indicated in the service URI
Comment 3 Rigo Wenning 2004-04-26 14:04:51 UTC
I re-arranged all completely and added the jurisdiction element  
under it's own point: