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 4671 - [Full text LC draft sec. 3.3.6] Why wild card options, not regular expressions?
Summary: [Full text LC draft sec. 3.3.6] Why wild card options, not regular expressions?
Status: CLOSED WONTFIX
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Full Text 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-20 07:10 UTC by Felix Sasaki
Modified: 2008-02-12 00:50 UTC (History)
0 users

See Also:

Attachments

Description Felix Sasaki 2007-06-20 07:10:59 UTC 
In 3.3.6, you define wild card options. I am wondering why you are not reling on on existing regular expression syntax like XML Schema regular expressions and would propose to do so.
Comment 1 Jochen Doerre 2007-06-26 17:02:28 UTC 
Hello Felix,

The FTTF considered your problem report in its F2F, June 2007.
Here is our answer:
There was no perceived user requirement to have full regular expression support,
and implementers were worried about the additional complexity in a part of the
full/text engine where regular expressions are usually not supported.
We have chosen to support wildcards in a way that actually uses syntax which
is compatible with regular expressions. Hence, when a requirement to have
more complete regular expression support should come up, we can add this support
without backward imcompatibility.
Does this answer your question? If yes, could you please close the bug.
Comment 2 Felix Sasaki 2008-02-12 00:50:01 UTC 
Apologies for late reply, I did not see the comment at
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4671#c1
I'm fine with this bug being closed.

Felix