TR/xquery-operators/#func-xpath-id and TR/2003/WD-xpath-datamode l-20030502/#recently-closed-issues

Issue-0004: Schema/DTD says:

Date: Oct-2000

Raised by: Datamodel Editors

Description: A document may refer to a DTD and have an associated schema.
Currently, content model from the DTD is ignored, as are unique IDs from the
schema. A coherent priority or merging strategy is needed.

Any strategy developed must also address the issue of types derived from
xs:ID.

Resolution: Infoset-only processing is performed if and only if schema
processing was not.
http://lists.w3.org/Archives/Member/w3c-xsl-query/2003Jan/0117.html



So how does this align with 

15.4.2 fn:id
fn:id($srcval as xs:string*) as element* 
Returns the sequence of element nodes with ID values matching the values of
one or more of the IDREF values supplied in $srcval. Each string in $srcval
is parsed as if it were of type xs:IDREFS, that is, $srcval is treated as a
space-separated sequence of tokens, each acting as an IDREF. These tokens
are then included in the list of candidate IDREFs. 


The data model implies I've lost the id attributes of type ID,
the function implies all params of fn:id() are id values of type IDREF?

Is this a contradiction?

More importantly,
  Two documents:
   Second identical to the first, except that it is well formed only.
  the first defines id values as being of type ID.

With 1.0
In the first I can use the id() function.
In the second the function effectively fails.

What's the position with 2.0 for these two cases?

regards DaveP
AC RNIB 


Regards DaveP.

**** snip here *****

- 

NOTICE: The information contained in this email and any attachments is 
confidential and may be legally privileged. If you are not the 
intended recipient you are hereby notified that you must not use, 
disclose, distribute, copy, print or rely on this email's content. If 
you are not the intended recipient, please notify the sender 
immediately and then delete the email and any attachments from your 
system.

RNIB has made strenuous efforts to ensure that emails and any 
attachments generated by its staff are free from viruses. However, it 
cannot accept any responsibility for any viruses which are 
transmitted. We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email 
and any attachments are those of the author and do not necessarily 
represent those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk 

Received on Monday, 12 May 2003 06:58:17 UTC