Hi Gopal and all,
I've just committed a copy of AbstractNumericDV that Neeraj had sent me
privately. This solved all but one compilation error--one array hadn't
been initialized, so I initialized it to a completely arbitrary value (see
a REVISIT in DateTimeDV for details).
I'm committing all t
Hi David,
--On Freitag, 5. Oktober 2001 17:24 +0200 David DELGRANCHE
<[EMAIL PROTECTED]> wrote:
> I'm looking for a C++ implementation of XML Signature. In fact, I would
> like to sign XML documents using a Java API (perhaps XML Secure Suite)
> and would to verifiy them in a C++ applicat
Hi all,
I'm looking for a C++ implementation of XML Signature. In fact, I would
like to sign XML documents using a Java API (perhaps XML Secure Suite) and
would to verifiy them in a C++ application. So I'm just looking for an
implementation that enables me to verify the
Hello
I am parsing xml-files that have a doctype-declaration with the name of
their (system) dtd written into.
Usually I have to specify in the doctype-declaration the relative path
of the dtd if I want it to be found by the DOMParser. Instead we want
this dtd to be found automatically in the cl
Andy Clark wrote:
>
> Reviewing what is currently in Xerces2, checked into the
> impl.v2.datatypes package, we have a datatype validator
> factory interface for creating datatype instances and we
> have a datatype validator interface for doing the actual
> validation of datatype values. By usin
>From the build failure report, the DTM compilation relies on
>the way that pull-parsing was performed in the past. Since
>this has changed in Xerces2, this code would need to be
>updated before it could be used with Xerces2.
How much has changed? My dependencies are currently on SAXParser,
SAXP
Andy wrote:-
> Gopal Sharma wrote:
> > The problem is due to the non-availability of AbstractNumericDV. Because of
> > this, the code is not compiling there.I am sending the AbstractNumericDV.
>
> I'm having problems with the design of the datatype stuff
> that you guys are working on.Could you
>Andy Clark wrote:
> I started looking at the code that has been checked into the
> impl.v2.new_datatypes package and I'm having a few problems
> with the code.
Seems as one of the class was missing,so there was compilation problem.
as it has been sent so that problem should be solved. W
We need to be able to validate DTD and XML Schema datatypes.
I consider the DTD datatypes core and essential because they
are defined as part of the XML syntax in the XML 1.0 spec.
The XML Schema datatypes are defined for use with XML Schema
structures but have also been borrowed by other schema
Andy Clark wrote:
> REQ #1: Validate DTD and XML Schema datatypes.
> REQ #2: Share datatype validators among multiple grammars.
> REQ #3: Be able to interchange datatype library.
> REQ #4: Provide standalone implementation.
> REQ #5: Allow applications to define new datatypes.
REQ #6: Support ret
Okay, let's start from the beginning and build from there
as we discuss what features we need in a datatype validator
implementation. First, some requirements. Granted, these
are *my* requirements but I will use them in the course of
my design discussions.
REQ #1: Validate DTD and XML Schema da
Gopal Sharma wrote:
> The problem is due to the non-availability of AbstractNumericDV. Because of
> this, the code is not compiling there.I am sending the AbstractNumericDV.
I'm having problems with the design of the datatype stuff
that you guys are working on. Could you please reply to my
post t
Aleksander Slominski wrote:
> wouldnt it be better to throw an exceptionif user tries to set
> features that are not allowed in this state of the parser?
You're absolutely right -- someone just needs to implement it.
I'm waiting for your patches. :)
> it just took me a bit of time to figure out
13 matches
Mail list logo
