- From: Julien Reichel <Julien.Reichel@spinetix.com>
- Date: Tue, 21 Oct 2008 11:00:00 +0200
- To: "Dr. Olaf Hoffmann" <Dr.O.Hoffmann@gmx.de>, <www-svg@w3.org>
Hi Olaf and all, Just a note. When using both id and xml:id there might be some issue with scripting. According to [1], scripting will modify only the xml:id and thus the effect will be different if the UA uses xml:id or not. This should be taken into consideration if modifying the "priority" of svg:id compared to xml:id. Julien [1] http://www.w3.org/TR/2008/WD-SVGMobile12-20080915/struct.html#IDAttrHand ling -----Original Message----- From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] On Behalf Of Dr. Olaf Hoffmann Sent: samedi 18 octobre 2008 18:36 To: www-svg@w3.org Subject: Re: [1.2T-LC] Less Emphasis on 'xml:id' Hello SVG WG, in general, it is unedifying that xml:id came so late into the XML play, but looks quite useful, if someone wants to create a more complex compound document from different formats. Especially if one has to point to a fragment of another document, it is obviously a simplification, if always the same attribute is used to identify a fragment, this may help for some RDF, WAI-ARIA, XHTML:role approaches too, including unambiguous CURIEs. Therefore the general idea that authors should use it and implementors should implement it, will get important in the near future, if authors really start to create such compound documents and meta information and helps more often. For SVGT1.2 and backwards compatibility to older browsers I cannot see a real problem, why authors should not always note both id and xml:id with the same value, if possible - and surely for SVGT1.2 only documents it is always possible and not really an unreasonable demand for any halfway intelligent author ;o) Olaf
Received on Tuesday, 21 October 2008 09:00:40 UTC