[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Gutenberg Project <longish>

  • From: Jon Noring <noring@n...>
  • To: xml-dev@x...
  • Date: Wed, 8 Mar 2000 09:04:01 -0800 (PST)

Re: Gutenberg Project <longish>
THOMAS PASSIN <tpassin@i...> wrote:

>After reading a lot of the postings in this thread, no one except the GP
>itself seem to be looking at the key issue namely, ***who will be creating
>the markup, and how can they do  a lot of it?***.  As far as I can see, it
>is likely to be volunteers who don't know much or care about markup and
>DTDs.  I imagine that they will want to:

In the e-book publishing DTD I envision (my thoughts posted under a different
thread), this aspect is a very important consideration in my book.


>1) Get on with the job with a minimum of things to learn up front and
>remember,
>2) Be able to know how to write their markup by looking at a few samples,
>3) Have the markup make sense at first or second glance,
>4) Minimize their typing,
>5) Easily see the results of their work, probably as they go along.
>6) Know that mistakes they make will not cause disasters.
>7) Use some helpful software as long as it is simple, easy to understand,
>and faster to use than plain typing.
>
>Any document design you come up with needs to meet these points ***first***
>because otherwise you won't get much markup produced nor many people to do
>it.  It looks like the GP people have already found this out.

In general, I agree with this.


>As to configurable DTDs for widespread interchange, this looks like a great
>place for keeping everything as close as possible to a single standard
>version, or at least a ***very*** few variations.  This would support
>non-paid volunteers, and public-domain software development, as well as the
>development and interchangable use of readers...
>
>I don't know much about TEI, but the only way it could work would be 1) you
>can really simpify it, and 2) you can rename elements to be evocative than
><div type="...">.  Preferably you want the element name to do the work, not
>an attribute (attributes like "type" go against points 1 and 4).  TEI people
>can speak to this, I don't know enough.

My other post earlier today outlined the two basic approaches to higher-
level structuring:  use <div type="...">, or create elements for all the
oft-used divisions (e.g., <titlepage>, <chapter>, <section>, <preface>,
<glossary>, etc.)  It is not a trivial issue.

Jon Noring
Yomu


***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.