XMLmind XML Editor Personal Edition v4.5.1 can be downloaded from
http://www.xmlmind.com/xmleditor/download.shtml

Professional Edition users, please upgrade using this form:
http://www.xmlmind.com/store/download.php

(The above form is usually accessed through
http://www.xmlmind.com/xmleditor/upgrade.html.)
     _____________________________________________

XMLmind XML Editor v4.5.1 (November 26, 2009):

   * New submenu "View > Display Images" allows to
     display images as thumbnails, as bounding boxes
     or normally. The selected mode may be used as a
     default.

   * Thanks to XMLmind DITA Converter 1.1.0, DITA
     documents can now be converted to Eclipse
     Help.

   * Among several other functions, new menu item
     "Options > Customize Configuration >
     Preprocessing Options" makes it easy specifying
     a DITA conditional processing profile (a
     .ditaval file) from within XXE.
     _____________________________________________

More information:
http://www.xmlmind.com/xmleditor/changes.html


--
XMLmind XML Editor Support List
xmleditor-support@...
http://www.xmlmind.com/mailman/listinfo/xmleditor-support

XMLmind XSL-FO Converter Personal Edition v4.3.2 can be downloaded from
http://www.xmlmind.com/foconverter/downloadperso.shtml

Professional Edition users, please upgrade using this form:
http://www.xmlmind.com/store/download.php

(The above form is usually accessed through
http://www.xmlmind.com/foconverter/upgrade.html.)
     _____________________________________________

v4.3.2 (December 4, 2009):

More powerful, yet nicer and easier to use, XMLmind XSL
Utility.

Out of the box, in addition to DocBook and XHTML documents,
XMLmind XSL Utility now allows to convert DITA 1.1 documents
to production-quality XHTML 1.0, XHTML 1.1, HTML 4.1,
Java[tm] Help, HTML Help, Eclipse Help, PDF, PostScript®,
RTF (can be opened in Word 2000+), WordprocessingML (can be
opened in Word 2003+), Office Open XML (.docx, can be opened
in Word 2007+), OpenOffice (.odt, can be opened in
OpenOffice.org 2+).
     _____________________________________________

More information:
http://www.xmlmind.com/foconverter/changes.html



--
XMLmind FO Converter Information List
xfc-announce@...
http://www.xmlmind.com/mailman/listinfo/xfc-announce

SQL Transparent Multipath Hierarchical Structured
Data Processor with Dynamic XML Publishing

An ANSI SQL Transparent XML Multipath Hierarchical Processor prototype has
proven a number of newly discovered relational and hierarchical inherent SQL
capabilities that can be of use to the dynamic publishing of structured data and
it's dynamically XML formatted output. This new level of full dynamic structured
data processing and output is also being applied to the full multipath nonlinear
hierarchical query processing. This introduces the capability to produce new
nonlinear hierarchical processing and XML capabilities where the publishing
industry is in a position to utilize these new basic capabilities first. These
areas involve: Structured authoring; Delivery formats; Single sourcing;
Organization strategies; Transforming XML content; and Interactive operation. A
new paper that documents these new capabilities described below and produced and
demonstrated from the prototype can be found at:
http://www.slideshare.net/mmdavid/ansi-sql-transparent-xml-structured-data-multi\
path-hierarchical-processing-with-dynamic-output-2360420

This prototype integrates relational data and native XML data at a full lossless
multipath hierarchical processing level. It naturally supports the dynamic and
hierarchically semantic accurate joining of physical (XML) and logical
(relational) hierarchical structures. The prototype has a hierarchically
structure-aware operation which enables it to output the dynamically processed
hierarchical result automatically in its resulting hierarchical structured XML
format. Different XML output styles are selectable. The hierarchical processing
and output format is further dynamically controlled by SQL's SELECT list which
allows the output to be interactively specified from query to query aiding
significantly in dynamic publishing ease, flexibility and accuracy of use. Only
the hierarchical nodes with data selected are output. This results in
hierarchical node promotion and node collection to be naturally performed by
default.This automatically generates an intuitive and concise XML result
enabling dynamic publishing of structured data processing. The SQL SELECT list
operation also efficiently and dynamically controls and tailors the hierarchical
processing necessary to support only the output results necessary.

Since SQL is a navigationless language, so is the XML access and processing in
the prototype. XML hierarchical structures today are basically limited to linear
path processing because of the hierarchical user navigation which makes
multipath processing extremely difficult and complex. The prototype's true
nonprocedural navigationless processing of hierarchical structures makes
unlimited querying of hierarchical multipath structures possible even by non
technical users. It is no concern of the users what the structure of the data is
or whether multiple hierarchical pathways are being queried. This internal
navigation is carried out automatically and correctly. This is known as
schema-free querying. It is also not generally known outside of academic XML
research that multipath hierarchical processing also requires a complex
processing logic known as Lowest Common Ancestor (LCA) logic which is needed to
control the processing between the pathways to keep the result meaningful.
Academic XQuery research is currently experimenting with adding this LCA logic
on top of XQuery using LCA functions. ANSI SQL's inherent hierarchical
processing automatically supports this powerful LCA processing inherently which
is being leveraged by the prototype.

The prototype's hierarchical optimization enables SQL views to be global
containing full hierarchical structure view definitions without any overhead
attached to their flexible use. The SQL SELECT list processing operation
described above only accesses the necessary nodes in the specified structures.
Multipath queries dynamically increase the value of the data by naturally
utilizing the natural hierarchical structure semantics that exist naturally
between every set of pathways. This allows a simple data filtering specification
using SQL's WHERE clause data filtering to operate across entire SELECTed
hierarchical structures. This should be very useful for dynamic publication and
reuse. This multipath data filtering capability is known academically as XML
Keyword Search. This capability also requires LCA processing and is performed
automatically and correctly in the SQL used in the prototype.

All of the above dynamic hierarchical processing capabilities can be tested
interactively and online using the prototype at www.adatinc.com/prototype.html.
It contains full documentation and sample data. One last new capability
important to XML publication is the ability to perform hierarchical structure
transformations using the new hierarchical technology in the prototype's SQL
operation to support semantically controlled any-to-any hierarchical structure
transformations performed using ANSI SQL hierarchical processing. In SQL this
becomes easier to specify, more accurate to perform and supplies the capability
to perform it. This new transform can be tested too.

Michael M David
Advanced Data Access Technologies, Inc.
www.adatinc.com






[Non-text portions of this message have been removed]

$Id: guidelines.txt,v 1.20 2003/06/02 01:47:07 smith Exp $

xml-doc list guidelines
-------------------------------------------------------------------
   These guidelines are sent as a Welcome message to new xml-doc
   subscribers and once every four weeks to all current
   subscribers.  Please save these guidelines for later reference
   and take a moment to review them now, including the PRIVACY
   POLICY and NO-SPAM NOTICE at the end.

TABLE OF CONTENTS
-------------------------------------------------------------------
   0. TOPIC GUIDELINES
   1. ACCESSING THE XML-DOC WEB SITE
   2. POSTING AND REPLYING TO MESSAGES
   3. READING MESSAGES VIA THE WEB AND ACCESSING THE MESSAGE ARCHIVE
   4. UNSUBSCRIBING, RECEIVING DIGESTS, AND PUTTING MAIL ON HOLD
   5. DEALING WITH E-MAIL ATTACHMENTS
   6. RECEIVING FURTHER HELP

   A. PRIVACY POLICY
   B. NO-SPAM NOTICE
   C. NOTE ON TOPIC DRIFT, TROLLS, AND FLAMES
   D. CHANGELOG
-------------------------------------------------------------------

  0. TOPIC GUIDELINES
  -----------------------------------------------------------------
     xml-doc is for discussion of XML/SGML and document authoring,
     particularly authoring of documentation for computer software
     and hardware. Topics for which list members have a specific
     interest include:

       * XML editing applications
       * Single-sourcing for multiple audiences/delivery formats
       * XML-based content management systems
       * DocBook and other document-oriented markup vocabularies
       * Converting legacy documents
       * Organizational strategies for structured authoring
       * Document analysis and markup model design/refinement
       * Transitioning from older (e.g. FrameMaker) environments
       * Publishing (transforming and delivering XML content)

     Please also take a moment to read the NOTE ON TOPIC DRIFT,
     TROLLS, AND FLAMES at the end of this message.

  1. ACCESSING THE XML-DOC WEB SITE
  -----------------------------------------------------------------
     As a member of the xml-doc mailing list, you also have access
     to the xml-doc Web site:

       http://groups.yahoo.com/group/xml-doc/

     To use some features of the Web site, you also need to
     choose a username and password and register with Yahoo Groups.

  2. POSTING AND REPLYING TO MESSAGES
  -----------------------------------------------------------------
     To send a message to all the members of the mailing list,
     e-mail it to:

       xml-doc@yahoogroups.com

     To post a message via the Web, visit:

       http://groups.yahoo.com/post/xml-doc/

     By default, when you reply to a message, the reply is sent to
     all members of the list. If you want to reply just to the
     author of a posted message, please specify only the author's
     e-mail address in the "To:" field in your reply.

     Here are a few general tips for posting and replying to
     messages delivered to online mailing lists:

     a. Use meaningful subject lines.

        Try not to use generic, uninformative subject lines such as
        "Easy question," "Help needed," "Urgent," and so on.
        Instead, use meaningful subject lines that will quickly
        make sense to the people whose help you are trying to get.

     b. Quote only relevant parts of messages when replying.

        When replying to a message, please don't quote the author's
        entire message unless it's really necessary. Instead,
        quote just the parts to which you are directly replying, or
        quote only enough to establish a context for your reply.

     c. Avoid idiomatic and colloquial English.

        Be sensitive to the fact that a significant number of
        subscribers to any English-language online mailing list are
        non-native speakers of English. By avoiding idiomatic and
        colloquial language, you ensure that your message will have
        a higher degree of international readability.

     Please also take a moment to read the NOTE ON TOPIC DRIFT,
     TROLLS, AND FLAMES at the end of this message.

  3. READING MESSAGES VIA THE WEB AND ACCESSING THE MESSAGE ARCHIVE
  -----------------------------------------------------------------
     All messages posted to the list are simultaneously posted to
     xml-doc website and are immediately available at:

       http://groups.yahoo.com/messages/xml-doc/

     All messages are also automatically archived. To search
     the archive, use the search box on the message page. To browse
     the archive by month, visit the xml-doc main page:

       http://groups.yahoo.com/group/xml-doc/

  4. UNSUBSCRIBING, RECEIVING DIGESTS, AND PUTTING MAIL ON HOLD
  -----------------------------------------------------------------
     You can unsubscribe at any time by e-mailing a message to

       xml-doc-unsubscribe@yahoogroups.com

     To specify that you want to receive a digest of messages once
     a day instead of receiving messages one at a time as they are
     posted, send a blank e-mail message to:

       xml-doc-digest@yahoogroups.com

     To remain a list member, but receive no mail (for example, if
     you plan to read messages by accessing the archive at the
     xml-doc Web site or if you want to stop your xml-doc e-mail
     while you are on a vacation), send a blank e-mail message to:

       xml-doc-nomail@yahoogroups.com

     To switch back from the "digest" or "no mail" settings to the
     "normal" setting, send a blank e-mail message to:

       xml-doc-normal@yahoogroups.com

     You can also change your delivery settings from the xml-doc
     Web site:

       http://groups.yahoo.com/subscribe/xml-doc/

  5. DEALING WITH E-MAIL ATTACHMENTS
  -----------------------------------------------------------------
     Any files that members attach to a message are stripped out
     before the message is distributed to the list; you cannot send
     or receive attachments via the list.

     If you have a file you would like to make available to the
     other members of the list, upload it directly to the file
     sharing area of the xml-doc Web site:

       http://groups.yahoo.com/files/xml-doc/

     All interested members can then access or download the file at
     their convenience.

  6. RECEIVING FURTHER HELP
  -----------------------------------------------------------------
     If you have questions about the list itself and need to have
     them answered by a real person, send them to:

       xml-doc-owner@yahoogroups.com

  Regards,

  Michael Smith
  xml-doc moderator and list owner

..................................................................

  A. PRIVACY POLICY
  -----------------------------------------------------------------
     The xml-doc list moderator has a complete list of e-mail
     addresses for all xml-doc subscribers, but will not provide
     any subscriber e-mail addresses or personal information to any
     third party, at any time, for any purpose. Yahoo Groups itself
     has a separate privacy policy:

       http://privacy.yahoo.com/

     Read their policy carefully and make sure it is acceptable to
     you. If it's not, you should unsubscribe from the list.

  B. NO-SPAM NOTICE
  -----------------------------------------------------------------
     Please don't post messages to xml-doc that are not related
     directly to XML/SGML and document authoring. Specific types of
     messages that are inappropriate on the list include:

     * Product or service announcements that have an excessive
       amount of unobjective marketing hype

     * Any "for sale" announcements; for example, if you have used
       computer equipment or software you're trying to re-sell, or a
       domain name you want to unload, posting an announcement to
       xml-doc is not an appropriate way to try to find a buyer

     You should also read the the Yahoo Terms of Service document,
     which contains information about their policy toward spam, along
     with other things.

       http://docs.yahoo.com/info/terms/

  C. NOTE ON TOPIC DRIFT, TROLLS, AND FLAMES
  -----------------------------------------------------------------
     Before posting or replying to a message, please remember this
     list's stated purpose -- as outlined in the TOPIC GUIDELINES --
     and show consideration for the fact that there are subscribers on
     the list from a wide variety of professional backgrounds, and
     that many people aren't going to be nearly as interested as you
     might be in any particular discussion that drifts away from the
     topic guidelines, no matter how important/relevant you may
     personally believe the particular topic drift to be.

     [0] http://www.catb.org/~esr/jargon/html/T/topic-drift.html

     xml-doc is a relatively low-noise list, and relatively free
     from trolls[1] and flames[2] and flame bait[3].

     [1] http://www.catb.org/~esr/jargon/html/T/troll.html
     [2] http://www.catb.org/~esr/jargon/html/F/flame.html
     [3] http://www.catb.org/~esr/jargon/html/F/flame-bait.html

     To help keep the noise level down, don't fan the flames, and
     avoid feeding the trolls if/when they appear (a much better
     strategy is simply to ignore them).

  D. CHANGELOG
  -----------------------------------------------------------------

     2003-06-02  <smith@...>

       * updated jargon-file URLs

     2003-05-02  <smith@...>

       * formatting tweak

       * changed vim foldlevel

       * minor reformatting

       * formatting, minor updates

       * topic drift, etc. section updated

     2002-10-04  <smith@...>

       * added section about topic drift, trolls, and flames (in another place)

       * added section about topic drift, trolls, and flames

     2002-07-02  <smith@...>

       * changed 'DocBook and other DTDs' to 'DocBook and other markup
vocabularies'

       * changed 'DTD creation' to 'markup model design'

     2002-04-24  <smith@...>

       * minor tweaks

       * removed spam warnings

       * expanded tabs

       * added more no-spam warnings

       * no-spam.txt: New file.

     2002-04-03  <smith@...>

       * fixed minor typo

     2002-01-02  <smith@...>

       * branches:  1.1.1; Initial revision

       * added Id keyword

       * New file.

// this file best viewed with Vim 6.1 or greater ;)
// vim:foldmethod=indent:foldlevel=1

http://xavierstti.org/Bp2DRva4vs.html

Please ignore the following if you have no interest in XML-related training.

In Q1'2010 I will be in Europe a couple of times for some standards
meetings (OASIS and ISO) and conferences ( http://www.XMLPrague.cz
and PEPPOL) and I like to take advantage of my presence there by
offering Crane's hands-on training classes in the week before or
after each of the events, open to public subscription.

I'll be in Copenhagen in February and in Prague and Stockholm in March.

But it is a gamble to decide on which training class to offer and
find no-one is interested in that particular topic, because of hotel
and event obligations that need to be paid in advance or reserved
with the risk of forfeit.  We realize not many people in these
economic times have money for training, so we are now trying to
target our offerings specifically where we learn there is demand and
availability of students.

Last year's http://www.XMLPrague.cz conference was great and we did
our training adjacent to the conference and our students were
conference attendees.  The venue we have chosen again in Prague next
year has room for only 6 students (a large 14th century hotel room),
so if XML training at this time of year and in conjunction with the
conference is of interest to you, it would be important to sign up
your interest soon.

To address this urgency to start making plans, I am polling the
various XML lists for any interest in training in these cities early
next year.  If you are interested in hands-on training on any of
XSLT, XQuery, XSL-FO, the Universal Business Language or code lists
in XML, and you would be interested in attending, please let us know
and we will figure out what we can do.  To see the proposed dates,
please visit:

    http://www.CraneSoftwrights.com/forms/interest.php
    (the page has links to syllabi)

On the form, please indicate all of the offered dates that you would
be interested in, and we'll make a decision based on the response
level we get for each class and date.

Thanks!  Please direct any questions to me off-list.

. . . . . . . . . Ken

p.s. it hasn't been decided but I might be in Perth Australia in
January or February, so you won't see it on the form, but if you are
in that area, please let me know in a mail message if you are
interested in training on any of our subjects and we'll see about
setting up a publicly-subscribed class.

cc: XML-Dev, XSL List, XQuery Talk, XML-Doc, UBL Dev, CLR Dev,
Antenna House list, RenderX list, MarkLogic list

--
Vote for your XML training:   http://www.CraneSoftwrights.com/x/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/x/
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman                 mailto:gkholman@...
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/x/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

Gareth Oakes <lists@...> writes:

> Once you got to the second part with the xpointer, you made me think of
> XQuery because it seems you are wanting to do some sort of querying of
> XML content, treating it like a database.

I forgot about XQuery.  It does sound worth reading up on again.

> Alternatively I guess an XSLT could be used to resolve your document
> from the component parts.

... assuming I was proficient at that already. :-)

> Of course, either way, you need <chapter> in the final hierarchy to make
> your Docbook document valid for publishing.

That I expected.

> Regards the ID scheme, if your doctype (Docbook) defines an "id"
> attribute as type ID, then your XML document (the one that is resolved
> from the XInclude) must have a unique value for each "id". It's as
> simple as that. As you suggest, most people would use something like
> "week01_goals" or whatever instead of just "goals".

Thanks, Gareth.  I think that is key to my solution.

Bill
--
Bill Harris                      http://facilitatedsystems.com/weblog/
Facilitated Systems                              Everett, WA 98208 USA
http://facilitatedsystems.com/                  phone: +1 425 374-1845

Once you got to the second part with the xpointer, you made me think of
XQuery because it seems you are wanting to do some sort of querying of
XML content, treating it like a database.

Alternatively I guess an XSLT could be used to resolve your document
from the component parts.

Of course, either way, you need <chapter> in the final hierarchy to make
your Docbook document valid for publishing.

Regards the ID scheme, if your doctype (Docbook) defines an "id"
attribute as type ID, then your XML document (the one that is resolved
from the XInclude) must have a unique value for each "id". It's as
simple as that. As you suggest, most people would use something like
"week01_goals" or whatever instead of just "goals".

-Gareth

Bill Harris wrote:
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I've not used xincludes for a few years. Now I'm in the position where
> they could be handy, and I've forgotten too much (or they don't do what
> I want). So far, I haven't found the key in searching on zvon.org,
> xmlsoft.com, wiki.docbook.org,
> http://www.ibm.com/developerworks/xml/library/x-reuseinfo2/index.html?ca=drs-,
>
<http://www.ibm.com/developerworks/xml/library/x-reuseinfo2/index.html?ca=drs-,>
> http://www.sagehill.net/docbookxsl/ModularDoc.html#XincludeSelect,
> <http://www.sagehill.net/docbookxsl/ModularDoc.html#XincludeSelect,>
> http://www.w3schools.com/xlink/xlink_example.asp,
> <http://www.w3schools.com/xlink/xlink_example.asp,>
> http://www.w3.org/TR/xinclude/#points,
> <http://www.w3.org/TR/xinclude/#points,> and a few other places (including
> the archives here).
>
> Let's say I'm teaching a course that lasts 3 weeks. I want a file for
> each week's plan. Each week will have goals, steps in the plan, and
> homework assignments.
>
> I'd like to be able to produce a document that describes the full course
> as well as documents that describe each week of the course and documents
> that describe, respectively, the weekly goals, weekly plans, and weekly
> assignments. Those latter three documents will need section (or
> chapter) headings for the weeks plus the appropriate content.
>
> I'm using xmllint and docbook2pdf or another jade processor, although I
> could be convinced to change (I'm on Ubuntu).
>
> The top-level document for the full document might look like:
>
> <?xml version="1.0"?>
> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
> <http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd>">
> <book>
> <title>Course Title</title>
> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude
> <http://www.w3.org/2001/XInclude>" href="week01.xml" />
> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude
> <http://www.w3.org/2001/XInclude>" href="week02.xml" />
> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude
> <http://www.w3.org/2001/XInclude>" href="week03.xml" />
> </book>
>
> A sample week's document might look like
>
> <?xml version="1.0"?>
> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
> <http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd>">
> <chapter id="week01">
> <title>Week 1</title>
> <section id="goals">
> <title>Goals</title>
> <para>
> Some goals.
> </para>
> </section>
>
> <section id="steps">
> <title>Detailed Plan Steps</title>
> <para>
> I might put a list of steps here.
> </para>
> </section>
>
> <section id="homework">
> <title>Homework</title>
> <para>
> How to do the homework. What the assignments are.
> </para>
> </section>
>
> </chapter>
>
> xmllint --xinclude works fine. I've got two problems when running
> docbook2pdf.
>
> First, I now have multiple pieces with the same id, and docbook doesn't
> like that. Is there a natural organization I'm missing? Sure, I could
> give each id the form toplevelid.lowerlevelid or some such, but that
> gets wordy, and it may make the second part difficult.
>
> Second, even if I only include the first file, there's a problem when I
> want to include only parts of the file. I'd like a file something like
>
> <?xml version="1.0"?>
> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
> "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
> <http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd>">
> <book>
> <title>Course Title</title>
> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude
> <http://www.w3.org/2001/XInclude>" href="week01.xml"
> xpointer="goals" />
> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude
> <http://www.w3.org/2001/XInclude>" href="week02.xml"
> xpointer = "goals" />
> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude
> <http://www.w3.org/2001/XInclude>" href="week03.xml" xpointer="goals"/>
> </book>
>
> but that doesn't quite work. While I'd like the week0n chapters and
> week0n goals sections to be included, this only includes the section.
> DocBook is unhappy because it's missing a chapter element, and I'm
> unhappy because I know I wouldn't know what week it was if it had
> worked.
>
> Comments? Tips? I suspect it's simple.
>
> Thanks,
>
> Bill
> - --
> Bill Harris http://facilitatedsystems.com/weblog/
> <http://facilitatedsystems.com/weblog/>
> Facilitated Systems Everett, WA 98208 USA
> http://facilitatedsystems.com/ <http://facilitatedsystems.com/> phone:
> +1 425 374-1845
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkr3XxUACgkQ3J3HaQTDvd9xQQCfeM/c1Mk72X9phlFHuYRgfUJx
> cCcAn2IJoLxYMTWoYz7XbvoAolLYjEOe
> =xL8S
> -----END PGP SIGNATURE-----
>
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've not used xincludes for a few years.  Now I'm in the position where
they could be handy, and I've forgotten too much (or they don't do what
I want).  So far, I haven't found the key in searching on zvon.org,
xmlsoft.com, wiki.docbook.org,
http://www.ibm.com/developerworks/xml/library/x-reuseinfo2/index.html?ca=drs-,
http://www.sagehill.net/docbookxsl/ModularDoc.html#XincludeSelect,
http://www.w3schools.com/xlink/xlink_example.asp,
http://www.w3.org/TR/xinclude/#points, and a few other places (including
the archives here).

Let's say I'm teaching a course that lasts 3 weeks.  I want a file for
each week's plan.  Each week will have goals, steps in the plan, and
homework assignments.

I'd like to be able to produce a document that describes the full course
as well as documents that describe each week of the course and documents
that describe, respectively, the weekly goals, weekly plans, and weekly
assignments.  Those latter three documents will need section (or
chapter) headings for the weeks plus the appropriate content.

I'm using xmllint and docbook2pdf or another jade processor, although I
could be convinced to change (I'm on Ubuntu).

The top-level document for the full document might look like:

<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
                  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<book>
<title>Course Title</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="week01.xml" />
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="week02.xml" />
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="week03.xml" />
</book>

A sample week's document might look like

<?xml version="1.0"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
                  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="week01">
<title>Week 1</title>
<section id="goals">
<title>Goals</title>
<para>
   Some goals.
</para>
</section>

<section id="steps">
<title>Detailed Plan Steps</title>
<para>
   I might put a list of steps here.
</para>
</section>

<section id="homework">
   <title>Homework</title>
   <para>
     How to do the homework.  What the assignments are.
   </para>
</section>

</chapter>

xmllint --xinclude works fine.  I've got two problems when running
docbook2pdf.

First, I now have multiple pieces with the same id, and docbook doesn't
like that.  Is there a natural organization I'm missing?  Sure, I could
give each id the form toplevelid.lowerlevelid or some such, but that
gets wordy, and it may make the second part difficult.

Second, even if I only include the first file, there's a problem when I
want to include only parts of the file.  I'd like a file something like

<?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
                  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<book>
<title>Course Title</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="week01.xml"
xpointer="goals" />
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="week02.xml"
xpointer = "goals" />
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="week03.xml"
xpointer="goals"/>
</book>

but that doesn't quite work.  While I'd like the week0n chapters and
week0n goals sections to be included, this only includes the section.
DocBook is unhappy because it's missing a chapter element, and I'm
unhappy because I know I wouldn't know what week it was if it had
worked.

Comments?  Tips?  I suspect it's simple.

Thanks,

Bill
- --
Bill Harris                      http://facilitatedsystems.com/weblog/
Facilitated Systems                              Everett, WA 98208 USA
http://facilitatedsystems.com/                  phone: +1 425 374-1845
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkr3XxUACgkQ3J3HaQTDvd9xQQCfeM/c1Mk72X9phlFHuYRgfUJx
cCcAn2IJoLxYMTWoYz7XbvoAolLYjEOe
=xL8S
-----END PGP SIGNATURE-----