Zitat von Bruce D'Arcus <[EMAIL PROTECTED]>:

> Am trying to wrap up the new version of CSL and would like some
> feedback.
>
> Here's another, even flatter, and more generic possibility:
>
>        <metadata-type name="book">
>          <formatting-def name="author" alternate="editor"/>
>          <formatting-def name="year" prefix=" (" suffix=") "/>
>          <formatting-def name="title" font-style="italic" suffix="."/>
>          <formatting-def name="editor"/>
[...]

Hi Bruce

  Just some weeks ago I read on
<http://www.w3schools.com/xml/xml_attributes.asp> that it is good practice to
use elements for data and attributes for metatata only (e.g. "language" or "id"
or the "font-style" attribute as in the example above). I like to agree with
this:
  An XML structure based on elements is extensible in the future. You can later
define additional children or new attributes when necessary. If data is stored
in an attribute, this attribute cannot easily be extended to hold more
information in the future.
  Using usual XML parsers as I know them from Java it is not easier or more
difficult to parse or write elements than attributes. So except a slighly
smaller file you wouldn't gain much using these parsers. Of course I don't have
experience with Ruby or Phython but I don't expect it to be very different.

Anyway, my opinion is NOT to use such "flattened" layout.

P.S. Sorry for the long delay, but our mailing system had a crash last weekend.
Hope this helps.
Matthias Basler
[EMAIL PROTECTED]

----------------------------------------------------------------
This mail was sent through http://webmail.uni-jena.de

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to