[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Re: olink element question
Yes, setting xml:id="filenames" in the chapter element is fine. I'm not sure what you mean by "without any additional declaration", though. All elements in DocBook 5 allow an xml:id attribute, so putting one on the chapter element does not require any further declaration. You can put an xml:id on every element, and link to every element if you like. Perhaps the phrase "document id" is confusing you here. Like I said, it is not an official term, and it is not necessary to refer to an id with it. When you have <chapter xml:id="filenames">, the xml:id is associated with the element. That chapter element could be in its own file, or it could be included into a book, but the xml:id has the same status: an ID attribute on an element. So would it help to just drop the phrase "document id" and just refer to an id on an element? Bob Stayton Sagehill Enterprises bobs@sagehill.net ----- Original Message ----- From: "Karen Schneider" <kgschneider@gmail.com> To: "Bob Stayton" <bobs@sagehill.net> Cc: "docbook-apps" <docbook-apps@lists.oasis-open.org> Sent: Monday, September 07, 2009 9:33 AM Subject: Re: [docbook-apps] Re: olink element question > I think you are calling the id attribute of the root element of each file > the "document id", but that isn't an official XML term. It just means the > id of the document's root element. Ok -- I'm not as clear on this as I thought. In the following, can the xml:id function as the document id (without any additional declaration)? And therefore if this is in a book called book1 (xml:id book1), can it link to a file called graphics.xml (xml:id graphics) in book2 (<olink targetdoc="Book2" targetptr="graphics">use a graphic</olink>? <?xml version='1.0' encoding='UTF-8'?> <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="filenames"> <title>File Structure and Filenames</title> ... > > Perhaps "assembly" is a better term for the larger document that is > assembled for release as a unit. The targetdoc name is are associated with > such an assembly when dealing with modular content. That would help disambiguate things... methinks! -- -- | Karen G. Schneider | Community Librarian | Equinox Software Inc. "The Evergreen Experts" | Toll-free: 1.877.Open.ILS (1.877.673.6457) x712 | kgs@esilibrary.com | Web: http://www.esilibrary.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]