OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [docbook] Adding <para> to a <sect1> between <simplesect>


The required syntaxes--the shorthand (id) and element() scheme--do
not allow accessing all the children of an element.  As their names
imply, they allow accessing (1) any elements with an id and (2) any 
element (by reference to its position in the document hierarchy).

The required syntaxes for xpointer were designed to be used like
the fragment identifier in an HTML-referencing URI, and hence are
limited to things that can be processed quickly and easily, because 
such processors might be needed to dereference any URI in real time
over the web.  This is different from some XSLT processor where the
time it might take to do some more complicated XPath processing could 
be tolerated.

So being able to access all the children of an element is not a 
standard part of XPointer and may not be supported by a given 
XInclude implementation.

paul

> -----Original Message-----
> From: Rowland, Larry [mailto:larry.rowland@hp.com] 
> Sent: Monday, 2007 January 22 09:34
> To: Grosso, Paul; docbooklist
> Subject: RE: [docbook] Adding <para> to a <sect1> between <simplesect>
> 
> Paul,
> 
> Thanks for catching my oversight.  Yes, I was referring to 
> the optional
> XPATH-like syntax.  How would one use the required syntax to 
> access all
> the children of an element (I am afraid my experience with 
> XSLT left me
> with a better grasp of the XPATH syntax than with the 
> required xpointer
> schemes.
> 
> Regards,
> 
> Larry Rowland 
> 
> -----Original Message-----
> From: Grosso, Paul [mailto:pgrosso@ptc.com] 
> Sent: Friday, January 19, 2007 1:44 PM
> To: docbooklist
> Subject: RE: [docbook] Adding <para> to a <sect1> between <simplesect>
> 
> FWIW, note that you're talking about the "xpointer" attribute
> on the xinclude element in the XInclude standard [1], and
> the only values that an implementation must handle for
> this attribute are those defined by the XPointer Framework [2]
> and XPointer element() scheme [3] standards, neither of which
> would allow the asterisk syntax to which you refer.
> 
> It sounds like you are referring to some xpath-like syntax
> which is not a standard part of XPointer and which may not
> be supported by a given XInclude implementation.
> 
> paul
> 
> [1] http://www.w3.org/TR/2006/REC-xinclude-20061115
> [2] http://www.w3.org/TR/2003/REC-xptr-framework-20030325/
> [3] http://www.w3.org/TR/2003/REC-xptr-element-20030325/
> 
> > -----Original Message-----
> > From: Rowland, Larry [mailto:larry.rowland@hp.com] 
> > Sent: Friday, 2007 January 19 14:32
> > To: Chris Borg; docbooklist
> > Subject: RE: [docbook] Adding <para> to a <sect1> between 
> <simplesect>
> > 
> > The xinclude standard includes a syntax for selecting all 
> > children of an
> > element (the last characters in the xpointer attribute being 
> > a slash and
> > an asterisk (/*) specifies all children).  You would need to 
> > pick up the
> > title of the element separately, but it would allow you to 
> pull in all
> > the children and then add your own paras.
> > 
> > Regards,
> > 
> > Larry Rowland 
> > 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]