OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Suggestions for XML editors

I'm willing to maintain such a list of criteria for editors.

It's obvious that I concentrated on the features nowhere available (as far
as I now).
It's desirable to mention, if not describe, more basic features.

For instance, XED selects (in its "text" and only mode) at once the WHOLE
element when mousing over beginning of element, which 199$ worth XML Spy
doesn't do.

Also I forgot the instant enforcing (just after typing) of simple type and
key constraints, instead of batch enforcing as in XML Spy.

Vim has a nice instant coloring of syntax (erroneous or not).

etc etc ...

Maybe a list of keywords (thesaurus) to classify the features ?
And a matrix of features versus editors ?


-----Message d'origine-----
De : Michael Smith [mailto:smith@xml-doc.org]
Envoyé : jeudi 25 janvier 2001 13:32
À : Jean-Marc VANEL
Cc : xml-dev@lists.xml.org; office@xmlspy.com; jmvanel@free.fr;
Guillaume Rousse (E-mail); Thierry Madillo (E-mail); wwbota@free.fr
Objet : Re: Suggestions for XML editors

Jean-Marc VANEL <jmvanel@industrysuppliers.com> writes:

[regarding features that XML editors should have]

> What really would make the difference would be functionalities like:
> - selecting, cut-copy-paste, and advance cursor to node lists selected by
> XPath strings
> - edit through an XPath selection: hide all the rest not selected by the
> XPath (of course remember those XPath associated to the Schema)
> [...other good ideas]

It would be good to have an ongoing discussion about criteria for
editors, maybe eventually come up with an informal document describing
expected application behavior, and rationale for why it's expected.

Documenting desirable integration with related technologies (e.g.
XSLT/XPath things) is worthwhile, but a set of standard descriptions
of "basic" XML editor behavior would be good too-- For example, how an
editor should handle insertion of required elements and attributes,
insertion/choices from groups of required elements, selection of IDs
for IDREF attributes, etc.

> What about free software projects ?

A standard description of expected editing-application behavior would
give open-source developers and users common criteria to develop to
and evaluate against. Also for evaluating proprietary apps I guess

Michael Smith          mailto:smith@xml-doc.org
xml-doc                http://www.xml-doc.org/