Hi Robert,
I would suggest you take a look at the first candidate release of DocBook
5.1, available here:
http://docbook.org/xml/5.1CR1/rng/
The docbookxi.rnc file should answer your question, if you read RNC.
Feedback is solicited.
Bob Stayton
Sagehill Enterprises
[email protected]
--------------------------------------------------
From: "Robert Fekete" <[email protected]>
Sent: Tuesday, August 27, 2013 7:02 AM
To: <[email protected]>
Subject: Re: [docbook] Allowing arbitrary elements as the root of a DocBook
document
That's great news!
Will it also liberalize the use of xincludes? Now sometimes I get
validation errors when xincluding segments at weird locations.
Robert
On Monday, August 26, 2013 18:03 CEST, "Bob Stayton" <[email protected]>
wrote: > This problem was recognized after DocBook 5.0 was released.
DocBook 5.1 will liberalize this policy and allow just about any element
to
be the root element.
Bob Stayton
Sagehill Enterprises
[email protected]
--------------------------------------------------
From: "David Cramer" <[email protected]>
Sent: Monday, August 26, 2013 8:02 AM
To: <[email protected]>
Subject: [docbook] Allowing arbitrary elements as the root of a DocBook
document
> Users sometimes want to create DocBook documents such that some
> arbitrary element is the root (e.g. <table>) and then xinclude that
> file
> into a larger doc more than one time. The motivation is to avoid the
> need to put an id on the element but still be able to refer to it from
> an xi:include. The hitch is that if they validate this standalone file
> against the DocBook schema, it's not valid because it doesn't have
> book,
> chapter, section, etc as a root element. I've customized the schema in
> the past and am about to do that again, but it makes me wonder, what is
> the rational for only allowing a few elements to be the root of a
> DocBook document. If I want to create a DocBook document that has
> <table> or even <phrase> as its root element, why shouldn't it be
> considered valid?
>
> Regards,
> David
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
