What is my name?

[Stefan Monov]

Hee-hee, too bad Kopete's author didn't know about the "no bad associations
in other languages" guideline -- here, in Bulgaria, Kopete means "buy!", in
*imperative* form. It also looks *a lot* like "Kopele", which means "son of
a bitch". Not to mention that here Kexi is sometimes used as a derogatory
term for a fat guy. >_<

Anyway, I here are my suggestions (feel free to calmly ignore my K-ism,
Aaron):

Kuerist, Patternist, Kondukt, Konquerier, seeK, oaK, looKfor, investiKate,
Kolumbus, Kontent, reKuest, FlowtraK, Akcessance, Tranceform, Transq,
struKt, taKe, xtraKt

Notes:

Konquerier (con-query-er) could be either very confusing or very enchanting.
Dunno.

Kolumbus associates rightly, since the parser is like a sailor in the middle
of the XML ocean.

reKuest is twofold. It has the feeling of "ya" (yet another) in things like
yacc (since you'll RE-do the job of creating a XPath parser YetAnother
time). Also, what feels like the main thing here is the "Kuest", which has a
certain... adventure feeling to it, if you understand what I mean.

About FlowtraK... well, the parser kinda like tracks the XML flow.

"access" derivatives are particularly nice, since "access" summarizes both
original points - "change" and "navigate". Hence Akcessance.

I hope it's obvious that Tranceform is pronounced "Transform".

Transq feels cool, and signifies Transquery. Word-end q isn't patented by
Compaq, you know ;) .

struKt describes that we're changing/navigating a *structure*. Besides, it
feels a tad geeky, what with the C keyword "struct".

The parser "takes" things from the parsee, so enter, taKe.

Maybe the parser can be said to "extract" things from XML somewhat, so
xtraKt might work.

In the end, I don't see how the current name KXForm is bad or too general.
I'd stick with it.


On 5/28/06, Adriaan de Groot <groot at kde.org> wrote:
>
> On Sunday 28 May 2006 02:19, Aaron J. Seigo wrote:
> > On Saturday 27 May 2006 07:38, Frans Englich wrote:
> > > On Friday 26 May 2006 22:00, Aaron J. Seigo wrote:
> > > > that said, the XPath/XQuery/XSLT frameworks are built on top of the
> > > > KHTML / WebCore stuff, correct? does it then make sense to tie the
> name
> > > > in with that set of software?
> >
> > instead of hooking into the "web" part, what about "<something>Core". we
> > have WebCore, JavaScriptCore .... XMLCore? CoreXML?  you might have
> > something better for the <something> part, but by following this name
> > scheme we get something that provides a theme.
>
> This is about data query and transformation; can we do something about
> that?
> Taxons might make sense here, Core Compass perhaps for the steering and
> searching thing. Or call it "Brownian" for the random motion.
>
> > > What list is better? kde-devel?
> >
> > kde-promo =)
>
> Replying here anyway.
>
> --
> KDE Quality Team
> GPG: FEA2 A3FE
> _______________________________________________
> kde-quality mailing list
> kde-quality at kde.org
> https://mail.kde.org/mailman/listinfo/kde-quality
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-quality/attachments/20060528/5e1da3aa/attachment.html