W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2006

[Bug 3361] No defined behavior if external rules can't be accessed

From: <bugzilla@wiggum.w3.org>
Date: Mon, 19 Jun 2006 05:21:18 +0000
To: public-i18n-its@w3.org
Message-Id: <E1FsCCM-0000UU-Vu@wiggum.w3.org>


------- Comment #1 from fsasaki@w3.org  2006-06-19 05:21 -------
(In reply to comment #0)
> From MemoQ developers:
> Issue #2: "ITS doesn't define the procedure if rules defined in external
> resources aren't accessible (may ignore the existence of the unreachable
> link)."
> Comment from Yves:
> "Do we need to define a behavior for unreachable rules? Maybe just saying the
> processor should generate an error?"
> Comment from Sebastian:
> "I think we should say this is a fatal error."

I agree. One issue with this that we do not define any error behavior for ITS
processors, and I think ITS is simple enough to avoid long error descriptions
like e.g. in http://www.w3.org/TR/xslt20/#error-summary . Maybe it is enough to
stay with our "declarative" descriptions how external rules MUST (RFC 2119) be
interpreted, and add a non-normative ITS "processing" description. See also my
comment at http://www.w3.org/Bugs/Public/show_bug.cgi?id=3360#c0 .
Received on Monday, 19 June 2006 05:21:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:07 UTC