Re: [relax-ng] Requirements of compact syntax?

[James Clark <jjc@jclark.com>]

At a high level, I think we know what the requirements are: a compact,
readable, non-XML syntax that's appropriate for standardization (e.g. is a
good I18N citizen).  At a more detailed level, we have specific questions
relating to requirements that arise out of issues in the issues list; for
example, in the namespace declarations issues we have the question of to
what extent we should support translation from the RELAX NG XML syntax into
the compact syntax.  I'm not sure I see an intermediate level of detail that
we need to resolve as a prerequisite for deciding the detailed requirements
questions.  I think we should simply attempt to resolve the detailed
requirements questions as they arise in our discussion of issues on the
issues list.  Is there something you think we need to discuss before we
discuss the issue of the extent to which we should support translation from
the RELAX NG XML syntax into the compact syntax?

----- Original Message -----
From: <kohsuke.kawaguchi@sun.com>
To: "RELAX NG Mailing List" <relax-ng@lists.oasis-open.org>
Sent: Thursday, April 04, 2002 12:37 PM
Subject: [relax-ng] Requirements of compact syntax?


>
> It seems difficult to judge the necessity of a particular feature,
> without having some idea of requirements (or I should say "scope" of the
> compact syntax).
>
> It's not have to be rigid nor formal, but having some consensus about
> requirements/scope might help us resolve issues quickly.
>
> This namespace declarations issue might be one example. I feel it's OK
> to be not always possible to convert a RELAX NG XML syntax into a
> compact syntax.
>
>
> regards,
> --
> Kohsuke KAWAGUCHI                          +1 607 257 0037
> Sun Microsystems                   kohsuke.kawaguchi@sun.com
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
>
>