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 3941 - Pointing to stuff that's not there
Summary: Pointing to stuff that's not there
Status: RESOLVED FIXED
Alias: None
Product: ITS
Classification: Unclassified
Component: ITS techniques (show other bugs)
Version: WorkingDraft
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Felix Sasaki
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-01 14:57 UTC by Felix Sasaki
Modified: 2007-02-15 14:38 UTC (History)
0 users

See Also:

Attachments

Description Felix Sasaki 2006-11-01 14:57:07 UTC 
See thread at http://lists.w3.org/Archives/Public/public-i18n-its/2006OctDec/0027.html .
Original comment:
Suppose we have global rules such as 
<its:rules its:version="1.0">
		<its:translateRule selector="//msg/notes" translate="no"/>
		<its:locNoteRule locNoteType="description" selector="//msg/data" 
			locNotePointer="../notes"/>
		</its:rules>
And that the content looks like this:
<msg id="FileNotFound">
		<notes>Indicates that the resource file {0} could not be loaded.</notes>
		<data>Cannot find the file {0}.</data>
		</msg>
	<msg id="DivByZero">
		<data>Invalid parameter.</data>
		</msg>
There is no notes field in the second msg element.  Do we say somewhere in the spec what is supposed to happen in this case (since there *is* an element that matches the selector attribute)?
Comment 1 Felix Sasaki 2006-11-01 16:30:36 UTC 
Discussed at http://www.w3.org/2006/11/01-i18nits-minutes.html#item03 . Current position: no need to have new mechanisms (e.g. error conditions), maybe a "best practices".
Comment 2 Felix Sasaki 2006-12-20 15:52:26 UTC 
Resolved during http://www.w3.org/2006/12/20-i18nits-minutes.html#item05 :
"we don't need BP about XPath in the tagset document, maybe we can have this in the BP document"
Comment 3 Felix Sasaki 2007-02-15 14:38:58 UTC 
Moved the issue to BP document.