Next in thread →
Next in month →
Re: [docbook-tc] resource fragments
"Grosso, Paul" <> writes:
> fwiw, I note that xinclude uses the two attribute approach:
> an href attribute that is a URI reference without a fragment
> identifier and an xpointer attribute that gives just the
> fragment identifier.
Yeah, and I think that's probably the way to go.
>> -----Original Message-----
>> From: Bob Stayton [mailto:]
>> Sent: Tuesday, 2010 February 16 13:08
>> To: DocBook Technical Committee
>> Subject: [docbook-tc] resource fragments
>>
>> I have a question regarding referencing fragments of a resource. It
>> seems there could
>> be two ways to include a fragment of a resource in your document:
>>
>> 1. Define the resource element as a fragment, as in this example from
>> Larry's sample:
>>
>> <resource xml:id="svn.properties"
>> fileref="subversion/properties.xml#using.properties"/>
This is going to lead to:
<resource xml:id="svn.properties"
fileref="subversion/properties.xml#using.properties"/>
<resource xml:id="svn.builtins"
fileref="subversion/properties.xml#builtin.properties"/>
<resource xml:id="svn.xyzzy"
fileref="subversion/properties.xml#xyzzy"/>
which seems awfully redundant.
>> 2. Reference a fragment of a whole resource from a module:
>>
>> <resource xml:id="svn.properties"
>> fileref="subversion/properties.xml"/>
>> ...
>> <module resourceref="svn.properties#using.properties"/>
Yuck. Do not like. :-)
>> Perhaps a different syntax might work better:
>>
>> 3. Reference a fragment of a whole resource from a module using
>> another attribute:
>>
>> <resource xml:id="svn.properties"
>> fileref="subversion/properties.xml"/>
>> ...
>> <module resourceref="svn.properties" fragment="using.properties"/>
For consistency with XInclude, I propose we name the second attribute
xpointer.
Be seeing you,
norm
--
Norman Walsh <> | A proof tells us where to
http://www.oasis-open.org/docbook/ | concentrate our doubts.-- Anonymous
Chair, DocBook Technical Committee |
Next in thread →
Next in month →