13864 2011-08-22 18:03:26 +0000 broken links from datatype diagram 2012-02-21 01:33:31 +0000 1 1 1 Unclassified XML Schema Datatypes: XSD Part 2 1.1 only PC Linux CLOSED FIXED resolved P2 normal --- 1 saasha David_E3 cmsmcq www-xml-schema-comments oldest_to_newest 55585 0 saasha 2011-08-22 18:03:26 +0000 Hello! At http://www.w3.org/TR/xmlschema11-2/#built-in-datatypes there is a clicable SVG: http://www.w3.org/TR/xmlschema11-2/type-hierarchy-201104.svg which links to a description of each datatype, for example: http://www.w3.org/TR/CR-xmlschema11-2-20110721/datatypes.html#dateTimeStamp These links seem to be broken. Replacing the value of @xlink:href by (for example) http://www.w3.org/TR/xmlschema11-2/datatypes.html#dateTimeStamp (that is removing "CR-" and the date) may solve the problem. Regards! Saašha, 55878 1 cmsmcq 2011-08-26 15:27:33 +0000 Thanks for the bug report. The problem appears to be the result of an error in the generation of the published document; we will take steps to ensure that the problem is fixed in the next published version. W3C policy for maintaining the documents on the /TR page is that problems of this kind are to be fixed in the next publication of the document, not repaired in place. For issue management purposes, I'm marking this issue editorial. 64345 2 cmsmcq 2012-02-21 01:15:26 +0000 The problem with the links in the diagram of built-in datatypes appears to have been fixed in the production of the Proposed Recommendation published in January -- the version at http://www.w3.org/TR/xmlschema11-2/#built-in-datatypes does have the drawback that the links cause the browser to re-load the same document under a different URI, but the links are at least not broken in the current version. So I believe the problem reported here has now been successfully repaired, and I'm marking the bug as resolved. If the originator of the comment (saasha@acc.umu.se) can verify that the problem has been fixed, you are invited to close the bug in Bugzilla to signal your agreement that it's now fixed. (If you are unable to verify that the fix is successful, but instead discover that it has not been successful, please re-open the bug and explain.) If we don't hear from you either way, we'll assume you're content with the resolution of the issue (but busy). Thank you again for pointing out the problem.