Development of the lxml library

headers Robert Dailey | 1 Aug 23:02

_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev

Hi,
I'm interested in having a "schema typifier" for lxml.objectify that can
enrich an instance document with type information taken from an XML Schema (xsi:type and/or py:pytype).
Similar to the annotate()/pyannotate() stuff, but making use of the schema type definitions.

I'm wondering how one realized such thing best: Is there a possibility to make use of the lxml/libxml2
validation capabilities, i.e. to somehow hook this into the validation proceedings?

Any hints welcome,
Holger

--

-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

Hi Daniel,

Daniel Veillard wrote:
> On Thu, Jul 19, 2007 at 08:03:24PM +0200, Stefan Behnel wrote:
>> currently (as of libxml2 2.6.29), the schematron implementation writes
>> validation error messages to stderr with a plain fprintf in
>> xmlSchematronReportOutput (happily annotated with a "TODO").
>>
>> However, to make schematron usable in lxml, I need a way to propagate these
>> errors to the Python level. I would therefore like to see them passed into
>> __xmlRaiseError().
> 
>   The schematron code is really not complete, that sure could be fixed
> but a lot more may be needed. I asked for a definitive set of test for
> the ISO version and never got an answer, so I got discouraged and dropped
> working on it at the time. Of course now I have far less time for libxml2

Ah, that's too bad. Can you comment on how complete you consider the current
Schematron implementation?

Stefan

On Thu, Aug 02, 2007 at 01:52:05PM +0200, Stefan Behnel wrote:
> Hi Daniel,
> 
> Daniel Veillard wrote:
> > On Thu, Jul 19, 2007 at 08:03:24PM +0200, Stefan Behnel wrote:
> >> currently (as of libxml2 2.6.29), the schematron implementation writes
> >> validation error messages to stderr with a plain fprintf in
> >> xmlSchematronReportOutput (happily annotated with a "TODO").
> >>
> >> However, to make schematron usable in lxml, I need a way to propagate these
> >> errors to the Python level. I would therefore like to see them passed into
> >> __xmlRaiseError().
> > 
> >   The schematron code is really not complete, that sure could be fixed
> > but a lot more may be needed. I asked for a definitive set of test for
> > the ISO version and never got an answer, so I got discouraged and dropped
> > working on it at the time. Of course now I have far less time for libxml2
> 
> Ah, that's too bad. Can you comment on how complete you consider the current
> Schematron implementation?

  I would like to be able to answer. But 1/ first I don't fully remember
2/ I added support only for XPath1 tests, and the last version I saw
had support for XSLT1/2, I don't know how much is required to be
conformant, and if XSLT is needed, then the schematron support can't be
implemented within libxml2 (since it would depend on libxslt).
Basically I implemented based on a public spec, then it went to ISO
and now I don't have a test suite and it seems the final version 
doesn't look 100% like what I used for the implementation 
   One think missing in the implementation is include support, that's
for sure.

Daniel

--

-- 
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard      | virtualization library  http://libvirt.org/
veillard <at> redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine  http://rpmfind.net/

Hi,

I'm trying to install lxml-1.3.3 using easy-install, and it isn't so
easy. In particular (typescript edited for brevity):

Script started on Fri 03 Aug 2007 10:38:17 AM EDT
mwm$ sudo easy_install --verbose lxml==1.3.3
Searching for lxml==1.3.3
[...]
Best match: lxml 1.3.3
Downloading http://codespeak.net/lxml/lxml-1.3.3.tgz
Processing lxml-1.3.3.tgz
Unpacking lxml-1.3.3// to /tmp/easy_install-d0p9oh/lxml-1.3.3/
[...]
copying src/lxml/builder.py -> build/lib.linux-x86_64-2.5/lxml
running build_ext
building 'lxml.etree' extension
creating build/temp.linux-x86_64-2.5
creating build/temp.linux-x86_64-2.5/src
creating build/temp.linux-x86_64-2.5/src/lxml
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC
-I/usr/include/libxml2 -I/usr/local/include/python2.5 -c src/lxml/etree.c -o
build/temp.linux-x86_64-2.5/src/lxml/etree.o -w
gcc -pthread -shared build/temp.linux-x86_64-2.5/src/lxml/etree.o -L/usr/lib64 -L/usr/local/lib
-lxslt -lexslt -lxml2 -lz -lm -lpython2.5 -o build/lib.linux-x86_64-2.5/lxml/etree.so
/usr/bin/ld: /usr/lib64/libxslt.a(xslt.o): relocation R_X86_64_32 against `a local symbol' can not
be used when making a shared object; recompile with -fPIC
/usr/lib64/libxslt.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
error: Setup script exited with error: command 'gcc' failed with exit status 1
mwm$ exit
Script done on Fri 03 Aug 2007 10:39:03 AM EDT

Checking the mail list archives turns up building python
--enable-shared, and I did that, and nothing changed. The problem
appears to be with libxslt, not python in any case.

Anyone got any clues as to what to help with this?

       thanks,
       <mike
--

-- 
Mike Meyer <mwm <at> mired.org>		http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.

Mike Meyer wrote:
> I'm trying to install lxml-1.3.3 using easy-install, and it isn't so
> easy. In particular (typescript edited for brevity):
> 
> /usr/bin/ld: /usr/lib64/libxslt.a(xslt.o): relocation R_X86_64_32 against `a local symbol' can not
be used when making a shared object; recompile with -fPIC

You need to provide (export) the CFLAGS that apply to your platform,
especially the -fPIC option is required on x86_64.

Stefan

_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev

Hi Greg,

Greg Willden wrote:
> I love the etree stuff and I'm excited about the API additions that this
> team is adding to make it better.  Thanks for all your work.

:)

> I have a question about processing instructions and round trip file
> processing.
> Let's say I have a file 'test.xml' containing the following
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE project SYSTEM "test.dtd">
> <project><a><b/></a></project>
> 
> Then I run these commands
> 
> t1=etree.parse('test.xml')
> t1.write('testout.xml ', xml_declaration=True)
> 
> testout.xml looks like this:
> <?xml version='1.0' encoding='ASCII'?>
> <project><a><b/></a></project>
> 
> I see that t1.docinfo.doctype contains:
> <!DOCTYPE project SYSTEM "test.dtd">
> 
> So why isn't the PI written to the file?
> 
> I am parsing/modifying a file for consumption by another program that
> refuses to load the file without the PI.

Hmm, the problem here is that libxml2 lacks a good backwards compatible way of
serialising documents including things like processing instructions, internal
subsets (DTDs) and doctype declarations (which you have here, it's not a PI).

I'll look into it (once again). IIRC, we serialise PIs by now, but not
internal subsets and doctypes. We should do that when serialising root nodes
(especially ElementTree objects).

Stefan

_______________________________________________
lxml-dev mailing list
lxml-dev <at> codespeak.net
http://codespeak.net/mailman/listinfo/lxml-dev

jholg <at> gmx.de wrote:
> I'm interested in having a "schema typifier" for lxml.objectify that can 
> enrich an instance document with type information taken from an XML Schema
> (xsi:type and/or py:pytype). Similar to the annotate()/pyannotate() stuff,
> but making use of the schema type definitions.
> 
> I'm wondering how one realized such thing best: Is there a possibility to
> make use of the lxml/libxml2 validation capabilities, i.e. to somehow hook
> this into the validation proceedings?

Hmm, there was a similar question on the libxml2 mailing list recently about
creating a valid document from a schema. You might take a look there.

http://mail.gnome.org/archives/xml/2007-July/msg00073.html
http://mail.gnome.org/archives/xml/2007-August/msg00056.html

Stefan

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31

9	February 2012
46	January 2012
29	December 2011
33	November 2011
44	October 2011
29	September 2011
26	August 2011
28	July 2011
44	June 2011
42	May 2011
45	April 2011
46	March 2011
82	February 2011
8	January 2011
27	December 2010
36	November 2010
39	October 2010
68	September 2010
29	August 2010
80	July 2010
51	June 2010
72	May 2010
38	April 2010
83	March 2010
48	February 2010
81	January 2010
73	December 2009
88	November 2009
58	October 2009
60	September 2009
83	August 2009
100	July 2009
132	June 2009
51	May 2009
45	April 2009
54	March 2009
58	February 2009
68	January 2009
45	December 2008
104	November 2008
43	October 2008
42	September 2008
101	August 2008
136	July 2008
120	June 2008
110	May 2008
66	April 2008
75	March 2008
165	February 2008
75	January 2008
43	December 2007
30	November 2007
100	October 2007
111	September 2007
84	August 2007
146	July 2007
175	June 2007
95	May 2007
76	April 2007
55	March 2007
94	February 2007
20	January 2007
36	December 2006
63	November 2006
84	October 2006
121	September 2006
117	August 2006
61	July 2006
286	June 2006
281	May 2006
42	April 2006
136	March 2006
32	February 2006
23	January 2006
96	December 2005
263	November 2005
50	October 2005
41	September 2005
126	August 2005
29	July 2005
59	June 2005
78	May 2005
48	April 2005
22	January 2005
5	December 2004
28	November 2004
19	October 2004
6	September 2004

Re: lxml 1.3.3 released

schema typifier for objectify

Re: [xml] Catching error messages in schematron

Re: Catching error messages in schematron

easy_install of 1.3.3 not working

Re: easy_install of 1.3.3 not working

Round Trip w/ Processing Instructions (Newbie)

Re: Round Trip w/ Processing Instructions (Newbie)

Fwd: Round Trip w/ Processing Instructions (Newbie)

Re: schema typifier for objectify