2305 2005-09-26 12:41:51 +0000 stable fragment ids in specifications (editorial) 2005-09-28 14:02:49 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 1.0 Last Call drafts PC Windows XP CLOSED FIXED P2 normal --- 1 davidc chamberl public-qt-comments oldest_to_newest 6454 0 davidc 2005-09-26 12:41:51 +0000 I'm raising this issue on XQuery, but it probably relates to all documents, as they use the same build process, I think. Most sections use a stable fragment identifier but some use one that looks like the result of XSLT generate-id() For example appendix H (Glossary) may be referenced as http://www.w3.org/TR/xquery/#id-glossary but appendix I (Example applications) may be referenced (today) as http://www.w3.org/TR/xquery/#N1815A Apart from not looking so nice, if these IDs are automatically generated it means that they are _not_ stable and so the above URI reference will _break_ at the next draft as the copy in the undated URI is updated "in place". there are several other examples, as easily seen by hovering over the table of contents and watching the status line. Presumably this could easily be fixed by giving the sections ids in the xmlspec source or (as I did in MathML) modifying the stylesheets to use a more stable generated id (for example based on the sction number). David 6455 1 mike 2005-09-26 13:41:00 +0000 I think it would be a good idea to change the DTD to make the id attribute mandatory in the source, to prevent slip-ups. 6530 2 chamberl 2005-09-28 14:02:34 +0000 David, Thank you for this comment. On Sept. 28, 2005, the Query Working Group agreed with your suggestion. In future versions of XQuery specifications, all headings will have stable ID's. Since you labeled your comment as editorial and it was accepted by the working group, I have marked your comment as "Closed." Please feel free to reopen the comment if you have any further concerns or suggestions. Regards, Don Chamberlin