From: Jan Pokorný <jpokorny@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] config/tools/xml: validate resulting cluster.rng with relaxng.rng
Date: Thu, 7 Feb 2013 11:49:40 +0100 [thread overview]
Message-ID: <20130207104940.GB28345@redhat.com> (raw)
In-Reply-To: <511364C5.9010607@redhat.com>
Hello ,
On 07/02/13 09:24 +0100, Fabio M. Di Nitto wrote:
> Hi Jan,
>
> On 2/6/2013 9:47 PM, Jan Pokorn? wrote:
>> Doing so will guarantee the file is valid RELAX NG schema, not just
>> a valid XML.
>>
>> Validating schema, relaxng.rng, was obtained directly from [1] and
>> matches directly to a version bundled with xmlcopyeditor in Fedora 17.
>> The same (modulo VCS headers, comments and spacing details) can be
>> obtained by combining schema as in the specification [2] and its
>> errata [3].
>>
>> [1] http://relaxng.org/relaxng.rng
>> [2] http://relaxng.org/spec-20011203.html
>> [3] http://relaxng.org/spec-20011203-errata.html
>
> this looks like a good idea, but i have one question.
>
> Is there a specific reason why we need to ship/embed the file with our
> tarball? How bad is it to require the one installed on a system?
It is not bad at all, but you can hardly find it system-wide. AFAIK
there is no standard in packaging such standalone single files
anywhere yet (see also, e.g., JavaScript libraries, everything is
usually bundled). Once there is a wide-spread standard (if ever)
where such files are located within the distributions, relaxng.rng
can be dropped and dependency can be added.
> I can see it?s rather stable and hardly updated, but i prefer to avoid
> duplication if we can.
I share the same intention, however current situation does not seem
to be offering any other choice.
--
Jan
prev parent reply other threads:[~2013-02-07 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 20:47 [Cluster-devel] [PATCH] config/tools/xml: validate resulting cluster.rng with relaxng.rng Jan Pokorný
2013-02-07 8:24 ` Fabio M. Di Nitto
2013-02-07 10:49 ` Jan Pokorný [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130207104940.GB28345@redhat.com \
--to=jpokorny@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).