- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Fri, 16 Dec 2005 15:16:47 -0500
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: www-xml-linking-comments@w3.org
- Message-ID: <87ek4col00.fsf@nwalsh.com>
/ Bjoern Hoehrmann <derhoermi@gmx.net> was heard to say: | Dear XML Core Working Group, | | http://www.w3.org/TR/2005/WD-xlink11-20050707/ has been published as | Last Call Working Draft but I could not find responses that formally | address comments on the previous drafts, e.g. | | http://lists.w3.org/Archives/Public/www-xml-linking-comments/2005JanMar/0009.html With respect to the issues raised in this message, On the question of what applications are expected to do with nested links, we have no advice beyond what is currently in the specification. It is up to the application to decide how to deal with the link relationships exposed by the markup. On the question of CSS, we believe that question is (or will be) addressed by our response to http://www.w3.org/mid/430f85af.62527875@smtp.bjoern.hoehrmann.de On the question of what to do about mixed vocabulary linking (xlink:href and href), we belive that question is (or will be) addressed by our response to http://www.w3.org/mid/430d85ab.62524234@smtp.bjoern.hoehrmann.de | http://lists.w3.org/Archives/Public/www-xml-linking-comments/2005AprJun/0003.html The attributes in question are not required and different applications might reasonably choose to implement different defaults (or allow users to specify the defaults). What's more, the question is outside the scope of our charter. | Where can I find responses that formally address these comments? Please let us know if this response addresses your concerns. Be seeing you, norm -- Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc. NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Received on Friday, 16 December 2005 20:18:22 UTC