This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3361 - No defined behavior if external rules can't be accessed
Summary: No defined behavior if external rules can't be accessed
Status: CLOSED FIXED
Alias: None
Product: ITS
Classification: Unclassified
Component: ITS tagset (show other bugs)
Version: LastCall
Hardware: PC Windows XP
: P2 normal
Target Milestone: AfterLC
Assignee: Yves Savourel
QA Contact: Felix Sasaki
URL:
Whiteboard:
Keywords: changeDeclined, reviewerSatisfied
Depends on:
Blocks: 3360
  Show dependency tree / graph
 
Reported: 2006-06-19 02:30 UTC by Yves Savourel
Modified: 2006-10-15 00:39 UTC (History)
1 user (show)

See Also:

Attachments

Description Yves Savourel 2006-06-19 02:30:03 UTC 
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."
Comment 1 Felix Sasaki 2006-06-19 05:21:18 UTC 
(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 .
Comment 2 Felix Sasaki 2006-06-20 05:32:52 UTC 
Added István to the CC list.
Comment 3 Felix Sasaki 2006-07-24 12:54:25 UTC 
Action: working group to discuss and reply.
Comment 4 Felix Sasaki 2006-09-06 15:28:23 UTC 
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.
Comment 5 Felix Sasaki 2006-09-24 00:01:29 UTC 
No reply from commentor after two weeks. Closed.
Comment 6 Felix Sasaki 2006-09-28 06:11:37 UTC 
Summary: The Working Group decided not to define error conditions for non-accessible external rules.
Comment 7 István Lengyel 2006-10-14 17:43:55 UTC 
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.