W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2010

[Bug 9541] TokenInfo term confusing

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 May 2010 17:23:29 +0000
To: public-qt-comments@w3.org
Message-Id: <E1OBtB3-0007pR-LA@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9541


Paul J. Lucas <paul@lucasmail.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




--- Comment #2 from Paul J. Lucas <paul@lucasmail.org>  2010-05-11 17:23:29 ---
In private communication with Liam Quin, he suggested that if I "feel strongly
that [the name change] needs to be done now, please reopen the bug and we'll
reconsider."

OK, so I'm reopening it.  While the mere name of something might seem trivial,
it's important to choose good names and the earlier the better.  Names affect
how people talk about things, how implementers will name their data structures,
how others will write their own documentation, papers, books, etc.

Naturally, people will use the names used in the specification.  If a name is
confusing, it will only cause the confusion to proliferate.  If the name is
changed in a future release, then there will already be legacy documentation,
books, code, etc., that uses the old name.

Speaking as an XQuery Full Text implementor, XQuery, although being a rich and
expressive language, is quite a complicated language, both for users and
implementors.  Having clear names for things is a necessary foundation.

Thank you for your reconsideration.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 11 May 2010 17:23:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:42 UTC