[emacs-wiki-discuss] Re: Initial version of muse-xml.el

[drkm]

Michael Olson writes:

> <section title="Level 1 header">

  Mmh.  IMHO, 'title' could be better an XML element, instead of
an attribute.  So we can add markup to it.  For example:

    <section>
      <title>Level 1 <em>header</em></title>
      ...
    </section>

(ok, that's quite an artificial example, but this is the idea).

> Feel free to let me know of ways that this could be improved.  I'm not
> at all an XML guru :^) .  Likewise, if there's anything that I could
> add to it that would make Planner-XML publishing easier, let me know!

  See below.

> Thinking in advance: Once this gets solid and people are happy with
> muse-xml, it'd be great if someone could provide a DTD document for
> it, or whatever else is needed.  I'm not sure whether copyright would
> need to be assigned to the FSF for such a document to be included with
> Muse.  Do you know whether or not this is the case, John?

  [ IMHO, it would.  I don't see why the rules would be different
    for a DTD.  But I'm not a copyright guru. ]

> Thinking farther in advance: Eventually it would indeed be good to
> have such styles as poem-xml, book-xml, journal-xml, and so on.

  IMHO, the first thing to do is designing the type of document.
MuseXML could be generic, and accept elements of an other
namespace in a lot of places.  For example:

    <m:page xmlns:m="Muse namespace...">
      <p:tasks xmlns:p="Planner namespace...">
        <m:title>Tasks</m:title>
        <p:task priority="A">Design <m:em>MuseXML</m:em>.</p:task>
      </p:tasks>
      <m:section>
        <m:title>Schedule</m:title>
        ...
      </m:section>
      ...
    </m:page>

  With <p:tasks> deriving from <m:section>.  So one can easily
plug some Planner, Poem or Journal extension to MuseXML (to the
type definition as well as to the stylesheet).

  This could be a very interesting task to do, but unfortunatly I
don't have the time to investigate furthemore.  Maybe in a few
weeks.

--drkm