This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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."
(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 .
Added István to the CC list.
Action: working group to discuss and reply.
Discussed at http://www.w3.org/2006/09/06-i18nits-minutes.html#item14 . Resolution of the WG: the behavior is currently undefined. Implementors are encouraged to use common sense and generate errors when needed in implementing ITS processors. Wait: answer sent.
No reply from commentor after two weeks. Closed.
Summary: The Working Group decided not to define error conditions for non-accessible external rules.
We can accept the response. However, I feel that this will lead to numerous different implementations and the market may respond to this by trying to lock users in to use a certain implementation or another.