W3C home > Mailing lists > Public > public-svg-wg@w3.org > January to March 2009

RE: More on circular references

From: Alexander Adam <alexander.adam@examotion.com>
Date: Thu, 19 Mar 2009 13:13:10 +0100
To: "'Lee Martineau'" <lee.martineau@quickoffice.com>, <public-svg-wg@w3.org>
Message-ID: <CF7A4E7756744C8A86808F77A6E925E2@DellPM6300>
Hi!

Note: You might also want to allow circular references and provide a certain
nesting level in the spec. In renesis, we've made pretty good experience in
restricting to level to 8 levels. However, allowing such a thing allows to
produce some really interesting effects without the hassles to produce too
much svg code to reach the same.

mfG / Regards,
Alexander Adam
--
Geschäftsführer / CEO
 
examotion GmbH
Ostendstraße 115
90482 Nürnberg, Germany

Fon: +49 911 - 504901-11
Fax: +49 911 - 504901-20
 
E-Mail: alexander.adam@examotion.com
Web: http://www.examotion.com
 
Geschäftsführer: Alexander Adam
Amtsgericht Nürnberg HRB Nr.: 23803
Gerichtsstandort: Nürnberg
 

--------------------------------------------------
LEGAL DISCLAIMER: The information in this email is confidential and may be
legally privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it, is prohibited and may be unlawful.
--------------------------------------------------
 

> -----Original Message-----
> From: public-svg-wg-request@w3.org [mailto:public-svg-wg-request@w3.org]
> On Behalf Of Lee Martineau
> Sent: Donnerstag, 19. März 2009 13:09
> To: public-svg-wg@w3.org
> Subject: More on circular references
> 
> Hello WG,
> 
> As Cameron said in the March 16 telcon minutes, the objective is to
> eliminate having to provide "a highly perceivable indication of error".
> 
> In an embedded situation, there is generally no capability for logging or
> displaying error information to the end user, so any error condition that
> can reasonably be handled within the user agent is simply handled.
> 
> In anticipation of Doug's request for how to soften the circular reference
> error processing, I have provided a possible approach below.
> 
> http://www.w3.org/TR/SVGMobile12/struct.html#UseElement
> 
> Just before the schema is this sentence:
> 
> "However, a set of references that directly or indirectly reference a
> [sic] element to create a circular dependency is an error, as described in
> the References section."
> 
> How about:
> 
> "However, a set of references that directly or indirectly reference an
> element to create a circular dependency must be detected by the user
> agent.  The user agent may choose to handle the situation as an error (as
> described in the References section) or it may continue rendering until an
> implementation dependent limit on recursive processing is reached."
> 
> http://www.w3.org/TR/SVGMobile12/linking.html#ReferenceRestrictions
> 
> Buried in here is:
> 
> "A circular IRI reference is an error."
> 
> How about:
> 
> "A circular IRI reference must be detected by the user agent. Yada
> yada..."
> 
> --
> Lee Martineau
> 
Received on Thursday, 19 March 2009 12:14:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 19 March 2009 12:14:18 GMT