3361 2006-06-19 02:30:03 +0000 No defined behavior if external rules can't be accessed 2006-10-15 00:39:00 +0000 1 1 1 Unclassified ITS ITS tagset LastCall PC Windows XP CLOSED FIXED changeDeclined, reviewerSatisfied P2 normal AfterLC 3360 1 ysavourel ysavourel istvan.lengyel fsasaki oldest_to_newest 10108 0 ysavourel 2006-06-19 02:30:03 +0000 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." 10110 1 fsasaki 2006-06-19 05:21:18 +0000 (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 . 10150 2 fsasaki 2006-06-20 05:32:52 +0000 Added István to the CC list. 10707 3 fsasaki 2006-07-24 12:54:25 +0000 Action: working group to discuss and reply. 11407 4 fsasaki 2006-09-06 15:28:23 +0000 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. 11987 5 fsasaki 2006-09-24 00:01:29 +0000 No reply from commentor after two weeks. Closed. 12122 6 fsasaki 2006-09-28 06:11:37 +0000 Summary: The Working Group decided not to define error conditions for non-accessible external rules. 12478 7 istvan.lengyel 2006-10-14 17:43:55 +0000 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.