Hassan Schroeder wrote:
Geoff Deering wrote:
Can you please define "granular content" for me, and how it's collected?
<author>
<givenName/>
<middleInitial/>
<surName/>
</author>
That's granular; saying "This book was written by Joe W. Blow"
is not -- how does a machine pick the "author" out of that?
And you collect it with forms, like any other data.
So what is the problem with documents in OASIS ODF?
I think, in general, if you are customising scripts within an
application, and they are designed for that, then that is fine. But in
apps like IWTS you have to write many scripts in their Perl derivative
to get it to clean up a lot of stuff. If you are having to write any
new transformations that aren't part of the core app, that to me is
having to reinvent the wheel (to a very small extent). But I'm more
referring to having to write all these scripts to tie transformations
between applications together.
Now I'm not sure what you mean by "transformations between
applications".
Necessary transformation of document formating from application to
application, so that documents become interchangable.
Can you clarify your definition of content and document.
In Web terms, "content" is what's in each (non-presentational!)
element of a page: <p>, <cite>, <address>, etc. The "document"
is the page as a whole.
Content can quite validly refer to the whole collection of content
structured as grouped content in elements in a meaningful structure as a
whole. That was the context it was used in.
Can you please also explain your definition of "You *build* documents
to specific targets *from* granular content"?
Sure; you can take, say:
<product>
<product_number/>
<product_line/>
<short_description/>
<long_description/>
<long_description_dripping_with_marketing_gibberish/>
</product>
:: and create a document for a specific purpose from 1 or more
of those elements.
<quote>People may be used to it, but it's not suitable for input to a
content management system; "content" != "document"</quote>
So why is ODF not suitable?
What is your definition of "semantically structured"?
Headings, logical divisions -- anything that shows up in Word's
"outline" (I think it's called) panel.
So what's the problem with ODF?
-----------------------
Geoff Deering
*********************************************************
The CMS discussion list for http://webstandardsgroup.org/
*********************************************************