Hi Philippe,
philippe.favr...@continental-corporation.com wrote on 01/03/2013 11:22:41
AM:
> Hi Michael,
>
> What would you recommend me if i want to be able to "xpoint"
> elements or attributes with an approach close to xpointer scheme (xpath
like)?
My impression of
Hi Michael,
What would you recommend me if i want to be able to "xpoint" elements or
attributes with an approach close to xpointer scheme (xpath like)?
Is it possible to extend the xpointer framework to extend xerces so that
it can handle different scheme than the one already implem
Hi Philippe,
The goal at the time we were working on this was conformance to the
XInclude 1.0 specification [1] which only requires support for the
XPointer Framework and XPointer element() scheme.
Thanks.
[1] http://www.w3.org/TR/xinclude/#application
Michael Glavassevich
XML Technologies
Hello Michael,
Thank you for the reply.
In my case, i wanted to use xpointer mainly in the context of xinclude.
I do not well understand the reasons why only a part of xpointer has been
implemented (only the scheme element (e.g.: xpointer="element(/1/1/1)")).
For instance, I think it
Hello Philippe,
The XPointer support in Xerces-J is limited to what is required for
XInclude and is only usable within the context of XInclude.
There no plans to enhance it further.
Thanks.
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E
Hello all
I am a user of Xerces-J and plan to use the Xpointer feature which from
the specification i read seems to be very powerfull.
However after few tries, i realized that not all is yet completly
supported.
What is the strategy of Xerces in regard to this Xpointer feature ?
Will it be
Hi Leandro,
The XPointer support [1] in Xerces is currently limited to the XPointer
Framework and XPointer element() schemes. It is possible to do what you
want but it's a bit ugly. You would need N include elements, where N is the
number of elements in your document:
etc...
Thanks
Hi, I'm trying to include the xml inside the tags
(without the tags ) into another xml.
How can I do this using the xpointer attribute of the xinclude tag?
I'm using Apache Xerces for parsing the xml.
Thank
Michael Glavassevich schrieb am 31.03.2009 um 10:09:01 (-0400):
> Michael Ludwig wrote on 03/28/2009 12:39:14 PM:
>
> > Gareth Western schrieb am 02.02.2009 um 22:20:40 (+):
> > > Hi,
> > >
> > > I have an application which uses Xerces-J (2.9.0) to parse a large
> > > xml document which I'd l
provide even less than that.
> You could do without the new-fangled XInclude and XPointer stuff, by
> using [general] external parsed entities and entity references to
> organize your documents into physical components.
>
> http://www.w3.org/TR/REC-xml/#sec-physical-struct
>
>
in quite
handy here.
You could do without the new-fangled XInclude and XPointer stuff, by
using [general] external parsed entities and entity references to
organize your documents into physical components.
http://www.w3.org/TR/REC-xml/#sec-physical-struct
C:\dev\XML\entities :: dir /b
Hi Gareth,
Gareth Western wrote on 02/04/2009 03:27:02 PM:
> Oh, I spoke too soon. From [1]: "XOM supports XInclude including the
> XPointer element() scheme and bare name XPointers. It does not support
> the XPointer xpointer() scheme." Which I guess means it's in t
Oop. Forgot to reference my [1] in the other email. It's the XOM
Tutorial @ http://www.xom.nu/tutorial.xhtml#d0e1992
On Wed, Feb 4, 2009 at 8:27 PM, Gareth Western wrote:
> Oh, I spoke too soon. From [1]: "XOM supports XInclude including the
> XPointer element() scheme and bar
Oh, I spoke too soon. From [1]: "XOM supports XInclude including the
XPointer element() scheme and bare name XPointers. It does not support
the XPointer xpointer() scheme." Which I guess means it's in the same
boat as Xerces with respect to what's supported.
Perhaps I'm g
Michael: XOM looks like it might be what I'm looking for. I originally
tried to use the old XIncluder project from sourceforge[1] until I
realised I'd probably need to use XPointers (which XIncluder does not
support either).
Joseph: I had considered that, but the situation is already complex
enoug
> If you need support for other kinds of XPointers then you may want to
> take a look on the net at some of the other XInclude processors that
> are available. e.g. perhaps XOM [4] supports what you're looking for.
Another quick idea: It's possible to implement an XInclude subset as an
XSLT styl
Hi Gareth,
As you've noticed from the FAQ, Xerces' support for XPointer in XInclude is
limited to the XPointer Framework [1] and XPointer element() scheme [2].
This is the minimum support [3] required for a conforming XInclude
processor. There has been no discussion on expanding/enh
imilar to the following:
...
The schema prevents me from including the entire inner file, as that
would result in nested function-set elements, so ideally i'd like to
only include the functions from each inner file. XPointer looks like
it would be the answer to this, changing the
/flyboy/:
Seems to me, that this should pass schema validation, where
xmlns:xi=''http://www.w3.org/2001/XInclude";
Instead, xerces-j 2.9.0 schema validation gives:
'xpointer attribute must be present when href attribute is absent.'
This passes schema validation,
Seems to me, that this should pass schema validation, where
xmlns:xi=''http://www.w3.org/2001/XInclude";
Instead, xerces-j 2.9.0 schema validation gives:
'xpointer attribute must be present when href attribute is absent.'
This passes schema validation, but its not v
Or generate an element() scheme XPointer instead: element(/1/1/2)
Nikhil Dinesh <[EMAIL PROTECTED]> wrote on 03/30/2006 10:36:14 AM:
> Well, if JXPath gives you an XPointer from an XPath, why not just
generate
> an XPath for a node? It will obviously not be the most readable XPat
Do you have a snippit that can generate the an XPath expression? Does
XPath work with XInclude?
Thanks again!!
On 3/30/06, Nikhil Dinesh <[EMAIL PROTECTED]> wrote:
> Well, if JXPath gives you an XPointer from an XPath, why not just generate
> an XPath for a node? It will obviousl
Well, if JXPath gives you an XPointer from an XPath, why not just generate
an XPath for a node? It will obviously not be the most readable XPath, or
the most efficient (doing that is impossible). For example if you
have:
and you want an XPath for bar3, it could simply be:
child
JXPath can return an XPointer string from a given XPath expression.
How ever this is not all that usefull to me.
Does anyone know of a way to automaticly generate and XPointer string
from a given XML node?
Thanks again!
On 3/30/06, Michael Glavassevich <[EMAIL PROTECTED]> wrote:
> O
On Mon, 27 Mar 2006, Brian Demers wrote:
Can an XPointer string be generated from a given node? How about when
using XInclude and DOM parsing?
What about SAX parsing?
If you're looking for an API which does this, I don't know of one.
Thanks again!
-Br
Can an XPointer string be generated from a given node? How about when
using XInclude and DOM parsing?
What about SAX parsing?
Thanks again!
-Brian Demers
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e
Hi Andrew,
Xerces' XInclude processor is a streaming implementation so cannot handle
non-causal XPath axes. With the existing XInclude processor, the
xpointer() scheme could only be partially implemented. There are currently
no plans to support it.
Thanks.
"Andrew Ferguson" &l
users@xerces.apache.orgSubject: when might
xpointer() scheme be supported?
hi,
does anyone know when the xpointer() scheme might
be supported in XInclude inclusions?
any help appreciated,
thanks,
Andrew
SVI.getTypeDefinition();
> }
>
> Whereas I think possibly it should be "if (typeDef == null)"?
You're right. It should be checking if it's equal to null.
>
> Also, if it is of interest, I have made some hacks which results in the
> xpointer being resolve
();
}
Whereas I think possibly it should be "if (typeDef == null)"?
Also, if it is of interest, I have made some hacks which results in the
xpointer being resolved as I would expect. However, not being familiar
with the details of Xerces implementation, I suspect what I have done
Hi Gerrard,
The reason this isn't working for you is that in Xerces, schema validation
is performed on the result infoset produced by the XInclude processor.
(XInclude does not specify a processing order, so this was an
implementation decision.) When the XPointer is processed it isn&#x
Hi,
I am getting an "XPointer resolution unsuccessful" error when I have an
XInclude include element that has an xpointer attribute using the
XPointer element() Scheme and that begins with an NCName (i.e. a
shorthand pointer).
The include element I am using looks like:
The err
Title: Message
hi,
does anyone know when the xpointer() scheme might
be supported in XInclude inclusions?
any help appreciated,
thanks,
Andrew
33 matches
Mail list logo
