Re: [docbook-tc] DocBook Publishers documentation

[Scott Hudson <scott.hudson@schneider-electric.com>]

Hi Norm,

this is great! Thanks for pulling this together. Just a few comments:

I'd like to include some of the verbiage from the specification in the
Introduction that explains the purpose behind the schema, and a summary of
what has been added / removed. I can work with you on this if you'd like.

I did notice the dcterms:* entry, and agree that we need to figure out how
to display/reference these better.

HTML tables were explicitly removed from Publishers, though there is a
request to add them back in, it is not part of the approved schema.

Thanks and best regards,

--Scott

Scott Hudson |  Pelco by Schneider Electric | United States | API and
Integration - Strategy
Ph: +1-970-282-1952  | M: +1-720-663-7268 |
scott.hudson@schneider-electric.com






On 6/7/11 7:33 AM, "Norman Walsh" <ndw@nwalsh.com> wrote:

> Here's a first peek at an attempt to build a version of TDG for
> DocBook Publishers.
> 
> http://nwalsh.com/scratch/publishers/
> 
> I think the refpages and content models are correct, though I had to
> fix some serious problems with the Publishers schema to get them.
> 
> It's going to be a bit of a headache to get the text right. All
> references to elements that aren't in Publishers will have to be
> profiled out.
> 
> I'm tempted to invent a new profiling system for that:
> 
>   <phrase condition="in-schema">This is some text that
>   mentions <tag>programlisting</tag>. It only appears if
>   the schema being documented includes the programlisting
>   element.</phrase>
> 
> I'm not sure what the chapters should be for this book. Probably just
> an introduction and maybe "what's different".
> 
>                                         Be seeing you,
>                                           norm


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________