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

More on circular references

From: Lee Martineau <lee.martineau@quickoffice.com>
Date: Thu, 19 Mar 2009 07:08:57 -0500
To: "public-svg-wg@w3.org" <public-svg-wg@w3.org>
Message-ID: <A13D0B44629697468E9C6AE200CFD39A61A231FA9E@mailkeeper.mdigitalm.com>
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:09:39 GMT

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