From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Machine description, an alternativ using XML
Date: Thu, 26 Feb 2009 21:47:54 +0000 [thread overview]
Message-ID: <20090226214754.GB14149@shareable.org> (raw)
In-Reply-To: <B3970B92-0C56-4398-BE19-FF865C36BB04@web.de>
Andreas Färber wrote:
> >XML already has a way of describing objects (elements) attributes of
> >those objects (attributes) and objects nested within those objects
> >(nested elements).
>
> True, but XML itself does not allow for arbitrary graphs, only trees.
> Unless of course you start using RDF/etc., and then it's no longer a
> small expat dependency only.
Many things are naturally tree shaped most of the time, which avoids
the need to invent names for everything when you don't need to, and
keeps the text compact and clear for human editing.
Otherwise, graph relationships are easily expressed with id="myname"
in one place and ref="myname" in the other place. (Think like HTML
anchors). That's useful anyway for clarity sometimes.
> As a user I do prefer easily readable XML formats, like Virtual PC or
> VMware may use, but I understand that such PC-only formats do not
> provide enough flexibility to customize a full OF device tree for all
> the platforms and devices QEMU supports. Having a frontend tool to
> generate a machine configuration from another config file format
> seemed like the best compromise when we last discussed the topic.
I don't see what's PC-only about that _style_ of config file, or why
it wouldn't provide the flexibility.
Obviously VMware and Virtual PC's exact format is PC-only, but it
doesn't make sense to mimic them exactly.
-- Jamie
next prev parent reply other threads:[~2009-02-26 21:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 9:36 [Qemu-devel] Machine description, an alternativ using XML Jamie Lokier
2009-02-26 12:01 ` Torbjörn Andersson
2009-02-26 13:24 ` Steve Fosdick
2009-02-26 18:48 ` Andreas Färber
2009-02-26 21:47 ` Jamie Lokier [this message]
2009-02-26 19:41 ` Blue Swirl
-- strict thread matches above, loose matches on Subject: below --
2009-02-26 13:09 Jamie Lokier
2009-02-26 6:49 Torbjörn Andersson
2009-02-26 16:06 ` Paul Brook
2009-02-26 22:14 ` Anthony Liguori
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=20090226214754.GB14149@shareable.org \
--to=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
/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).