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 2802 - Public/system IDs on Notation
Summary: Public/system IDs on Notation
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: All All
: P4 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: thimble, easy
Keywords: resolved
Depends on:
Blocks: 4000
  Show dependency tree / graph
 
Reported: 2006-02-06 15:42 UTC by Sandy Gao
Modified: 2009-04-21 19:21 UTC (History)
0 users

See Also:

Attachments

Description Sandy Gao 2006-02-06 15:42:20 UTC 
1. In the mapping rules for notation 3.12.2

{public identifier} The ·actual value· of the public [attribute] 

Since "public" is now optional, shouldn't the above rule be changed to 
something similar to "system"?

{system identifier} The ·actual value· of the system [attribute], if present, 
otherwise ·absent·. 

2. In the description of the properties 3.12.1

{system identifier}
Optional if {public identifier} is present...
{public identifier}
Optional if {system identifier} is present...

So it seems that at least one of "public" and "system" attributes must be 
present in the schema document. This may warrant a clause in "Notation 
Definition Representation OK".
Comment 1 Sandy Gao 2006-11-22 05:22:45 UTC 
Proposal: to adopt the suggestion for #1. About #2, we don't normally repeat a state the same rule as both a component constraint and a representation one. The component constraint is sufficient. So no change for #2.

Resolution: adopted at 2006-10-17 telecon.