Cameron,

thanks once again for contributing your expertise and time.

given that we are now agreed, I propose to query this reasonably significant issue with the SVGWG.
I hope you will comment and contribute to the resolution.

regards

~:"

On 27 Mar 2008, at 21:40, Cameron McCormack wrote:

Hi Jonathan.

Jonathan Chetwynd:
you state:

Invalid values in xlink:href="" are one way of making a
<use> element in error.

but where is the evidence for your assertion?

I thought I had provided it in a previous e-mail
(http://markmail.org/message/7s2biahkzmv6pkxu):

The following rules apply to the processing of invalid URI references:

   * An invalid local URI reference (i.e., an invalid references to a
     node within the current document) represents an error (see Error
     processing), apart from the xlink:href attribute on the 'a'
     element and the properties that allow for backup values in the
case where the URI reference is invalid (see 'fill' and 'stroke').
   * …
   — http://www.w3.org/TR/SVG11/struct.html#HeadOverview

but looking over that quote again I see I overlooked the word “local”.

So I agree that my assertion is incorrect, if
externalResourcesRequired="true" has not been specified on the document:

* When attribute externalResourcesRequired has been set to true on the
   referencing element or one of its ancestors, then an unresolved
   external URI reference (i.e., a resource that cannot be located)
   represents an error (see Error processing).
   — http://www.w3.org/TR/SVG11/struct.html#HeadOverview

SVG doesn’t seem to require any particular behaviour in the case of a
missing external resource when externalResourcesRequired="false".

--
Cameron McCormack, http://mcc.id.au/
        xmpp:[EMAIL PROTECTED]  ▪  ICQ 26955922  ▪  MSN [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to