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 29681 - [XP31] FOAY0001 is not defined and/or not linked
Summary: [XP31] FOAY0001 is not defined and/or not linked
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XPath 3.1 (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: P2 editorial
Target Milestone: ---
Assignee: Josh Spiegel
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-02 08:58 UTC by Abel Braaksma
Modified: 2016-09-27 20:20 UTC (History)
1 user (show)

See Also:

Attachments

Description Abel Braaksma 2016-06-02 08:58:16 UTC 
There are five occurrences of FOAY0001 in XP31 but it is not linked (to FO31, where it seems to be defined) or defined in that spec.
Comment 1 Abel Braaksma 2016-06-02 09:35:40 UTC 
Actually, I see that all FO errors in FP are not linked, so maybe this is by design. But I find it confusing, as it is not clear in the text that it is about an FO error and searching for it in the spec does not give you the definition.

So I propose, if at all possible/feasible, to link these external errors or to give them a generic "see FO31" marker or something.