Hassan Schroeder wrote:
Geoff Deering wrote:
Just to take your example of granularity;
<author>
<givenName/>
<middleInitial/>
<surName/>
</author>
OK, so that was a bad -- as in misleading -- example; try this one
(real but extremely abbreviated):
<gem>
<commonName>ametrine</commonName>
<composition>silicon dioxide</composition>
<MOH>7</MOH>
</gem>
What does the above granular data have to do with ODF? :-)
And what does it have to do with DocBook as you suggested;
The approach I'm suggesting is to acquire the content with as high
a degree of granularity as possible. Look at something like the
DocBook (or Simplified DocBook) schema and imagine creating a form
to input that level of detail for a publication.
There's no <gem> in the DocBook schema.
I agree with you, that if you want to express your granular content with
this definition, you have to write your own schema. In certain
situations this could be the option to adopt, but in many large
organisations, where there are many departments, many complex documents
for both intranet and internet publication, ODF and similar would
provide the same abstraction of granular data with the following;
<define name="text-object-index">
<element name="text:object-index">
<ref name="sectionAttr"/>
<ref name="text-object-index-source"/>
<ref name="text-index-body"/>
</element>
</define>
<define name="text-object-index-source">
<element name="text:object-index-source">
<ref name="text-object-index-source-attrs"/>
<optional>
<ref name="text-index-title-template"/>
</optional>
<optional>
<ref name="text-object-index-entry-template"/>
</optional>
</element>
</define>
This would also suit smaller organisations who wanted a simple
publishing model, without the cost of implementing custom schemas, and
input forms, which for a lot of organisations, are just too impractical
an approach.
To try and get back to the original point, that using ODF with
Forrest/Axkit/Lenya, would allow transformation of documents into
various output formats, maintaining semantics and meta data without the
need for 3rd party products.
--------------
Geoff Deering
*********************************************************
The CMS discussion list for http://webstandardsgroup.org/
*********************************************************
