RE: [saml-dev] Why is ID of type ID, whereas InResponseTo is of type NCName? And why is AssertionIDRef of type NCName?

From
Cahill, Conor P <>
Date
2006-06-12T13:48:56+00:00
ID
8AEB79DC01BE994D8DE3FD02FA5B475B03C65349@orsmsx409
Thread
RE: [saml-dev] Why is ID of type ID, whereas InResponseTo is of type NCName? And why is AssertionIDRef of type NCName?
InResponseTo does not refer to an element in the same XML 
document so it should not be related to XML ID processing.

 

XML ID type is a special flag for parsers which enables 
them to match local document references.

 

I think the key is that both types allow/require the same 
format of data, but keeping them of different types is the right thing to do so 
that they are not interpreted as local references (which they 
aren't).

 

Conor

  

  
  From: Costello, Roger L. 
  [mailto:] 
Sent: Monday, June 12, 2006 8:40 
  AM
To: 
Subject: [saml-dev] 
  Why is ID of type ID, whereas InResponseTo is of type NCName? And why is 
  AssertionIDRef of type NCName?

  

  

  
Hi 
  Folks,

  
 

  
In saml-schema-assertion-2.0.xsd 
  it defines:

  
 

  
-        
  The ID attribute to be of type 
  ID

  
-        
  The InResponseTo attribute to be of type 
  NCName

  
-        
  The AssertionIDRef element to be of type 
  NCName

  
 

  
I thought that ID, InResponseTo, 
  and AssertionIDRef all contain the same type of value?  
  

  
 

  
The value of InResponseTo must 
  equal the value of an ID, and the value of AssertionIDRef must equal the value 
  of an ID, right?

  
 

  
If so, then why are they 
  declared to be of different types?

  
 

  
/Roger