- cxml-devel - mailman3.common-lisp.net

[cxml-devel] Real-world Example
by Steven Nunez 11 Jun '12

11 Jun '12

Greetings again, Perhaps a good example would be a real one. I'm starting with some simple functions, such as obtaining the model name, algorithm, etc, from the attached XML example. Can anyone provide an exemplary method for doing this? Below is my naive attempt, which are all failing miserably: (defun algorithm-name (model) "Returns the algorithm for the model" (stp:filter-recursively (stp:of-name "algorithmName" (stp:namespace-uri model)) model)) I know this one will (if it were working) return a list, but since I can't get past the namespace problem haven't bothered to go any further. That function, I assume, is a rather trivial one for someone with some good examples or knowledge to work from. Here's a slightly more difficult function: (defun model-coefficient-list (model) "Returns a nested list of the following structure: (<model-name>-coefficients (coefficient1 coefficient1-value) (coefficient1 coefficient2-value) ... (coefficientn coefficientn-value))" ...) Something like this would be good to put on the STP website. Regards, - Steve

1 0

[cxml-devel] namespace-uri usage
by Steven Nunez 11 Jun '12

11 Jun '12

Gents, Can anyone tell me why namespace-uri can't give me the namespace for this test file? <PMML version="4.0" xsi:schemaLocation="http://www.dmg.org/PMML-4_0 http://www.dmg.org/v4-0/pmml-4-0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.dmg.org/PMML-4_0"> <Header copyright="Steve Nunez" description="Sample for Namespace"> <Timestamp>2012-06-11T08:17:10.8</Timestamp> </Header> </PMML> * (defparameter *ns-test* (cxml:parse #p"ns-test.xml" (stp:make-builder))) * (stp:namespace-uri *ns-test*) This, and a few variations, give "There is no applicable method for the generic function". I suspect the answer is because I'm asking for the namespace of a document, whereas STP wants it for an element. That's fine, but different enough from the typical ways of XML processing to make figuring out how to use it rather difficult. Does anyone have any working examples of processing documents typically found 'in the wild'? I've read the test.lisp file, but it simply programatically creates elements and then tests for them. Some real-world examples, common idioms and best practices would be very helpful. Cheers, - SteveN

1 0

[cxml-devel] cxml-stp usage
by Steven Nunez 10 Jun '12

10 Jun '12

Greetings all, I'm a bit stumped by some of the STP functions and usage. The documentation is, well, a bit sparse, so it's not clear whether there really is a bug or I'm mis-interpreting what I'm reading. Here is a simple function that should return all the child nodes of an element with the local-name of 'RegressionModel': (defun function-name (document) "Return the PMML model type of the document" (stp:filter-recursively (stp:of-name "RegressionModel") (stp:first-child document))) According to the documentation of filter-recursively: Return a list of descendant nodes of node in pre-order, from which nodes that do not satisfy predicate have been removed.and that for of-name: This function creates a test function for nodes of this name. > >The function returned will return T if the argument is an instance of attribute or element and has the specified local-name and namespace URI, and will return NIL otherwise. > >If local-name is nil, only the namespace URI is considered for comparison. > and here's the local snippet of the xmls that I'm trying to filter for: #.(CXML-STP:ELEMENT > #| :PARENT of type ELEMENT |# > :ATTRIBUTES '(#.(CXML-STP:ATTRIBUTE > #| :PARENT of type ELEMENT |# > :VALUE "PolynomialRegression" > :LOCAL-NAME "algorithmName") > #.(CXML-STP:ATTRIBUTE > #| :PARENT of type ELEMENT |# > :VALUE "regression" > :LOCAL-NAME "functionName") > #.(CXML-STP:ATTRIBUTE > #| :PARENT of type ELEMENT |# > :VALUE "KNIME Polynomial Regression" > :LOCAL-NAME "modelName") > #.(CXML-STP:ATTRIBUTE > #| :PARENT of type ELEMENT |# > :VALUE "s_s_temp" > :LOCAL-NAME "targetFieldName")) > :BASE-URI "file://+/Users/nunez/src/lisp/pmml/polynomial-regression.xml" > :CHILDREN '(#.(CXML-STP:TEXT > #| :PARENT of type ELEMENT |# > :DATA " > ")So, there's an attribute with a local-name that matches the value in of-name. Why is this function always returning NIL? Is stp stable enough for production use? It's been a while since it's been updated. I'm new to XML with LISP, so if there's a better documented or easier way to process these documents, happy to take a different route. Finally, does anyone know why I need to pass the function the first child? Seem cxml-stp is getting tripped up on the first line of the xml file: <?xml version="1.0" encoding="UTF-8"?> and forcing me to manually grab the second element. Is there a convention or idiom I'm missing? Sample file attached. Cheers, - Steve

3 3

[cxml-devel] Exported symbols [was: Re: Possible bug in cxml-stp]
by Raymond Wiker 25 May '12

25 May '12

On Wed, May 23, 2012 at 12:02 AM, David Lichteblau <david(a)lichteblau.com>wrote: > Quoting Raymond Wiker (rwiker(a)gmail.com): > > Would it be an idea to add functionality similar to what > > plexippus-xpath provides via with-namespaces? I.e, a special variable > > that holds the current set of namespace tag/uri mappings, and have > > some some additional constructors that use split-qname to extract the > > tag and look-up the url from the current set of mappings. > > Possibly... cxml currently has such a macro only for its serialization > API, i.e. > > CL-USER> (cxml:with-xml-output (stp:make-builder) > (cxml:with-namespace ("a" "http://a") > (cxml:with-element "a:b" > (cxml:text "xyz")))) > #.(CXML-STP-IMPL::DOCUMENT > :CHILDREN '(#.(CXML-STP:ELEMENT > #| :PARENT of type DOCUMENT |# > :CHILDREN '(#.(CXML-STP:TEXT > #| :PARENT of type ELEMENT |# > :DATA > "xyz")) > :LOCAL-NAME "b" > :NAMESPACE-PREFIX "a" > :NAMESPACE-URI "http://a"))) > > That API can't really modify STP in place though; the builder only knows > how to set up a full document. > [Subject: changed, as it was getting embarassingly inappropriate.] I ended up modifying my add-element function, based on the code that you included earlier. It now looks like this: (defun add-element (parent element-name attributes &optional element-value) (let ((element-name (if (listp element-name) (first element-name) element-name)) (namespace-uri (if (listp element-name) (second element-name) (cxml-stp:find-namespace (cxml::split-qname element-name) parent)))) (let ((new-element (cxml-stp:make-element element-name namespace-uri))) (cxml-stp:append-child parent new-element) (loop for (name value) on attributes by #'cddr do (cxml-stp:add-attribute new-element (cxml-stp:make-attribute (princ-to-string value) name (cxml-stp-impl::find-attribute-namespace (cxml::split-qname name) new-element)))) (when element-value (cxml-stp:append-child new-element (cxml-stp:make-text (princ-to-string element-value)))) new-element))) This seems to work, but I'm not 100% sure of the code that handles namespaces for attributes. Note that the code uses two un-exported symbols: cxml::split-name and cxml-stp-impl::find-attribute-namespace. Should these be exported? Best Regards, Raymond Wiker

1 0

[cxml-devel] Possible bug in cxml-stp
by Raymond Wiker 23 May '12

23 May '12

I'm using cxml-stp to build XML responses for a web service that implements Microsoft's "Research" API (actually, this is just a generalised search interface). While building this, I found something that looks like a bug in cxml-stp. If this is _not_ a bug, I'd be happy for any hint about what I'm doing wrong :-) The attachment contains a small test case which builds an XML document and serializes it. The attachment should be compiled and loaded after cxml-stp has been loaded, and the commented-out test form at the end of the file should then be evaluated. The test uses two implementations of cxml-stp-impl::collect-local-namespaces. With the original implementation, the "Status" and "Providers" elements get incorrect xmlns attributes. With the modified version, this is not the case.

4 9

[cxml-devel] non-canonical printing
by Cyrus Harmon 07 Apr '12

07 Apr '12

Currently, it seems that non-canonical printing always does this: <foo> bar</foo> Is there an easy way to make that print is <foo>bar</foo>, besides resorting to canonical mode? I can see the case for a new line (and appropriate indentation) for something like this: <foo> <moose> bar</moose> </foo> but I'd still rather see that as: <foo> <moose>bar</moose> </foo> thanks, Cyrus

1 1

[cxml-devel] RNG question
by Cyrus Harmon 06 Mar '12

06 Mar '12

So I'm trying to parse a schema that has the following in it: property-attach = element attach { element parameters { fmttypeparam? & encodingparam? }?, value-uri | value-binary } In order to get this to work with cxml-rng, I have to do the following: property-attach = element attach { element parameters { fmttypeparam? & encodingparam? }?, ( value-uri | value-text ) } Is the former invalid RNC or is cxml-rng's parser barfing where it shouldn't? A complete, minimal-ish example is shown below and attempting to parse it gives: failed to parse compact syntax at char 552, file://+/Users/sly/projects/cl-vcard/foo.rnc: Unexpected terminal CXML-RNG::|\|| (value CXML-RNG::|\||). Expected one of: (NIL CXML-RNG::} CXML-RNG::DOCUMENTATION-LINE CXML-RNG::[ :INCLUDE CXML-RNG::IDENTIFIER :START :DIV CXML-RNG::|)| CXML-RNG::CNAME CXML-RNG::|,|) [Condition of type CXML-RNG:RNG-ERROR] Thanks, Cyrus # Hacked together from the RELAX NG Schema for iCalendar in XML default namespace = "urn:ietf:params:xml:ns:icalendar-2.0-hack" value-text = element text { xsd:string } value-binary = element binary { xsd:string } value-uri = element uri { xsd:anyURI } encodingparam = element encoding { element text { "8BIT" | "BASE64" } } fmttypeparam = element fmttype { value-text } property-attach = element attach { element parameters { fmttypeparam? & encodingparam? }?, value-uri | value-text } start = element icalendar { property-attach+ }

2 4

[cxml-devel] validating without parsing?
by Cyrus Harmon 01 Mar '12

01 Mar '12

cxml and cxml-rng folks, I see that I can use a validator like so (from the examples): (cxml:parse-file "example.xml" (cxml-rng:make-validator (cxml-rng:parse-schema #p"example.rng") (cxml-dom:make-dom-builder))) But is there any way I can validate an already parsed (in-memory) XML (preferably STP) document? thanks, Cyrus

2 2

[cxml-devel] ELS 2012, Zadar, Croatia
by Marco Antoniotti 01 Feb '12

01 Feb '12

Apologies for the multiple postings. PAPER SUBMISSION DEADLINE EXTENDED European Lisp Symposium 2012, Zadar, Croatia, April 30th - May 1st, 2012 http://european-lisp-symposium.org The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, and so on. We encourage everyone interested in Lisp to participate. The main theme of the 2012 European Lisp Conference is "Interoperability: Systems, Libraries, Workflows". Lisp based and functional-languages based systems have grown a variety of solutions to become more and more integrated with the wider world of Information and Communication Technologies in current use. There are several dimensions to the scope of the solutions proposed, ranging from "embedding" of interpreters in C-based systems, to the development of abstractions levels that facilitate the expression of complex context dependent tasks, to the construction of exchange formats handling libraries, to the construction of theorem-provers for the "Semantic Web". The European Lisp Symposium 2012 solicits the submission of papers with this specific theme in mind, alongside the more traditional tracks which have appeared in the past editions. We invite submissions in the following forms: Papers: Technical papers of up to 15 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. Lightning talks: Abstracts of up to one page for talks to last for no more than 5 minutes. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. Important dates: February 15th 2012: submission deadline (extended deadline) March 7th 2012: acceptance results April 30th 2012: Conference opens Program Commitee. Chair: Marco Antoniotti, Università degli Studi di Milano Bicocca, Milan, ITALY Local organizers: Damir Cavar, Eastern Michigan University Franjo Pehar, University of Zadar Damir Kero, University of Zadar Members: Giuseppe Attardi, Università degli Studi di Pisa, Pisa, ITALY Pascal Costanza, Intel, Bruxelles, BELGIUM Marc Feeley, Université de Montreal, Montreal, CANADA Scott McKay, Google, U.S.A. Kent Pitman, U.S.A. Christophe Rhodes, Department of Computing, Goldsmiths, University of London, London, UNITED KINGDOM Robert Strandh, LABRI, Université de Bordeaux, Bordaux, FRANCE Didier Verna, EPITA / LRDE, FRANCE Taiichi Yuasa, Kyoto University, JAPAN -- Marco Antoniotti

1 0

[cxml-devel] ELS2012 Zadar, Croatia, Call for Papers
by Marco Antoniotti 23 Jan '12

23 Jan '12

Apologies for the multiple postings... =========================================================================== European Lisp Symposium 2012, Zadar, Croatia, April 30th - May 1st, 2012 http://european-lisp-symposium.org The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, and so on. We encourage everyone interested in Lisp to participate. The main theme of the 2012 European Lisp Conference is "Interoperabilty: Systems, Libraries, Workflows". Lisp based and functional-languages based systems have grown a variety of solutions to become more and more integrated with the wider world of Information and Communication Technologies in current use. There are several dimensions to the scope of the solutions proposed, ranging from "embedding" of interpreters in C-based systems, to the development of abstractions levels that facilitate the expression of complex context dependent tasks, to the construction of exchange formats handling libraries, to the construction of theorem-provers for the "Semantic Web". The European Lisp Symposium 2012 solicits the submission of papers with this specific theme in mind, alongside the more traditional tracks which have appeared in the past editions. We invite submissions in the following forms: Papers: Technical papers of up to 15 pages that describe original results or explain known ideas in new and elegant ways. Demonstrations: Abstracts of up to 4 pages for demonstrations of tools, libraries, and applications. Tutorials: Abstracts of up to 4 pages for in-depth presentations about topics of special interest for at least 90 minutes and up to 180 minutes. Lightning talks: Abstracts of up to one page for talks to last for no more than 5 minutes. All submissions should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates and http://www.acm.org/about/class/1998. Important dates: Jan 31st 2012: submission deadline Feb 21st 2012: acceptance results April 30th, 2012 Conference opens Program Commitee. Chair: Marco Antoniotti, Università degli Studi di Milano Bicocca, Milan, ITALY Local organizers: Damir Ćavar, Eastern Michigan University Franjo Pehar, University of Zadar Damir Kero, University of Zadar Members: Giuseppe Attardi, Università degli Studi di Pisa, Pisa, ITALY Pascal Costanza, Intel, Bruxelles, BELGIUM Marc Feeley, Université de Montreal, Montreal, CANADA Scott McKay, Google, U.S.A. Kent Pitman, U.S.A. Christophe Rhodes, Department of Computing, Goldsmiths, University of London, London, UNITED KINGDOM Robert Strandh, LABRI, Université de Bordeaux, Bordaux, FRANCE Didier Verna, EPITA / LRDE, FRANCE Taiichi Yuasa, Kyoto University, JAPAN

1 0

[cxml-devel] [PATCH][CXML-STP] Fix tests to work with :invert readtable case
by Jyrki Jaakkola 22 Jan '12

22 Jan '12

Changed with-ATTRIBUTE-test to with-attribute-test so that the calling code can find the macro as they were using with-attribute-test. Signed-off-by: Jyrki Jaakkola <jjkola at email dot com>

1 0

[cxml-devel] [PATCH] Fix :invert readtable case problems
by Jyrki Jaakkola 21 Jan '12

21 Jan '12

Fixed quite many cases where symbols were in uppercase. Also fixed one case where string was used as symbol name. There was also two cases of symbols which were missing vertical bars when the other occurences used them. Changes in klacks/klacks.lisp courtesy of Hans Hübner. Signed-of-by: Jyrki Jaakkkola <jjkola at email dot com>

1 0

[cxml-devel] [PATCH] map-node now converts non-string attributes and values to strings
by Daniel Lowe 10 Jan '12

10 Jan '12

While switching over from using xmls, I ran into a few problems with the conversion. Xmls will convert non-string attributes and values to strings, while cxml:map-node won't. Here's a patch to fix that. : Daniel : --- xml/xmls-compat.lisp | 18 ++++++++++-------- 1 files changed, 10 insertions(+), 8 deletions(-) diff --git a/xml/xmls-compat.lisp b/xml/xmls-compat.lisp index aa3d8bc..3804f8a 100644 --- a/xml/xmls-compat.lisp +++ b/xml/xmls-compat.lisp @@ -177,19 +177,21 @@ (defun map-node/qnames (handler node include-xmlns-attributes) (sax:start-document handler) (labels ((walk (node) - (when (node-ns node) - (error "serializing without :INCLUDE-NAMESPACE-URI, but node ~ + (when (node-ns node) + (error "serializing without :INCLUDE-NAMESPACE-URI, but node ~ was created with a namespace URI")) (let* ((attlist - (compute-attributes/qnames node include-xmlns-attributes)) - (qname (string-rod (node-name node))) + (compute-attributes/qnames node include-xmlns-attributes)) + (qname (string-rod (node-name node))) (lname (nth-value 1 (cxml::split-qname qname)))) (sax:start-element handler nil lname qname attlist) (dolist (child (node-children node)) (typecase child (list (walk child)) ((or string rod) - (sax:characters handler (string-rod child))))) + (sax:characters handler (string-rod child))) + (t + (sax:characters handler (string-rod (princ-to-string child)))))) (sax:end-element handler nil lname qname)))) (walk node)) (sax:end-document handler)) @@ -212,7 +214,7 @@ (string-rod lname)) :local-name (string-rod lname) :namespace-uri uri - :value (string-rod value) + :value (string-rod (princ-to-string value)) :specified-p t)) (xmlnsp (sax:make-attribute @@ -222,7 +224,7 @@ "xmlns")) :local-name (string-rod lname) :namespace-uri uri - :value (string-rod value) + :value (string-rod (princ-to-string value)) :specified-p t)))))) (node-attrs node)))) @@ -237,7 +239,7 @@ (if (or xmlnsp (not (cxml::xmlns-attr-p (string-rod name)))) (sax:make-attribute :qname (string-rod name) - :value (string-rod value) + :value (string-rod (princ-to-string value)) :specified-p t) nil))) (node-attrs node)))) -- 1.7.5.4

1 0

[cxml-devel] cxml install problem
by Noldus Reijnders 19 Dec '11

19 Dec '11

Hey all, When I try to install "cxml" through quicklisp:(ql:quickload "cxml") I get the following error:Attempt to set dispatch macro in system readtable #<readtable @ #x20107f7a>; copy readtable first. when it loads:"...\portableaserve-pre-lw6\libs\puri-1.3.1\src.fasl" Recompiling/reloading doesn't help. I tried copying the readtable, like it says in the error, but I'm not sure when/how to use copy-readtable (I'm not that experienced in Lisp (yet)), nor do I know what exactly causes the error. Is there perhaps someone that can help me? Or am I at the wrong place and should I look for puri help? Regards,Noldus PS I'm running Allegro CL.

1 0

[cxml-devel] [PATCH] A memory leak in klacks parser
by Kalyanov Dmitry 16 Nov '11

16 Nov '11

I've been trying to parse a relatively large XML file with Klacks and found what seems to be a memory leak inside Klacks parser. 1) When klacks sees the start of an element, an URI is pushed to the 'base-stack' field of 'context' structure ('klacks/element' calls 'p/sztag' which pushes the URI) but never actually removes it off the stack. 2) Similarly, klacks pushes the namespace to the 'namespace-stack' field of 'cxml-source' structure but never actually removes it off the stack ('klacks/element-2' pushes the namespace). Attached is a proposed patch that seems to fix these issues. With the patch, memory usage stays (almost) constant during parsing.

1 0

[cxml-devel] seeking suggestion for handling malformed attribute names
by Russell Kliese 29 Oct '11

29 Oct '11

I have been using closure-html and cxml to extract data from web pages. Up until now it has worked quite well, but I have come across a web page that has quite extraordinarily malformed html markup. I am looking for suggestions on how to continue parsing even when attribute names are malformed. Here is a self-contained example containing some of the offending markup: (require :closure-html) (require :cxml-stp) (defvar *html-str*) (setf *html-str* "<html> <body> <table> <tr><td vertical-align:=\"\" ;=\"\"></td></tr> </table> </body> </html> ") (chtml:parse *html-str* (cxml-stp:make-builder)) This example give CXML:WELL-FORMEDNESS-VIOLATION. I guess I could write a custom SAX handler to skip attributes with these errors, but is there a more simple solution? Should the chtml parser be patched to handle this case? Are there any other ways to make parsing more robust? Or is this markup beyond hope of repair? Regards, Russell

2 3

[cxml-devel] parsing from a http stream (no EOF at the end)
by Attila Lendvai 03 Oct '11

03 Oct '11

cxml:parse is stuck waiting for an EOF even after the last closing tag when parsing from a stream (in my case it's a http stream in a server entry point. the client waits for the server to react, the server waits for the EOF). looking at the code i get the impression that it was never meant to be used like this, an EOF is pretty much mandatory. could someone comment on this? was cxml ever meant to support such use-case, just noone really needed it yet? any plans for supporting this? any hints are appreciated, -- attila Notice the erosion of your (digital) freedom, and do something about it! PGP: 2FA1 A9DC 9C1E BA25 A59C 963F 5D5F 45C7 DFCD 0A39 OTR XMPP: 8647EEAC EA30FEEF E1B55146 573E52EE 21B1FF06

3 3

[cxml-devel] Will there be a release since 2008?
by Kalyanov Dmitry 05 Aug '11

05 Aug '11

CXML had not seen a release for a long time (last release was in 2008). The released version has some problems (e.g., ASDF2 will not load it and SBCL ships with ASDF2). I think that it would be easier for distribution maintainers (like Gentoo Portage Lisp team) if there would be a recent release of CXML. So I kindly ask CXML developers to make a release of CXML.

1 0

[cxml-devel] Ho do I write the following on a sink?
by Marco Antoniotti 30 May '11

30 May '11

Hi I am trying to write "Λ" on a sink. (let ((sink (cxml:make-character-stream-sink *standard-output* :indentation 2 :canonical nil))) (sax:start-document sink) (xhtml-generator:write-doctype sink) (xhtml-generator:with-html sink (:html (:head (:title "Titel")) (:body ((:p "style" "font-weight: bold") "Inhalt") (:ul (:li "Eins") (:li "Zwei") (:li "Λ") (:li "Drei"))))) (sax:end-document sink)) <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title> Titel</title> </head> <body> <p style="font-weight: bold"> Inhalt</p> <ul> <li> Eins</li> <li> Zwei</li> <li> &Lambda;</li> <li> Drei</li> </ul> </body> </html> #<EDITOR::RUBBER-STREAM #<EDITOR:BUFFER CAPI interactive-pane 2> 219C7A3F> How do I get it "right"? Thank -- Marco Antoniotti

4 9

[cxml-devel] A bug fix and a refactoring for consideration
by Russ Tyndall 02 May '11

02 May '11

I made a small bugfix and a refactoring of dom:map-document that I was hoping could be pulled upstream. Without the change to cxml:attribute*, attributes created with this function will not be serialized without setting the :include-default-values to T while when calling map-document. The map-document->walk refactoring was important so that I could map sub documents. I use this in my templating library (TALCL) to map nodes created in a dom document into a buffer of sax events (that can be played out during serialization). These are available from my github account: git pull git://github.com/bobbysmith007/cxml.git patches-on-upstream https://github.com/bobbysmith007/cxml/commits/patches-on-upstream If you need anything further from me, please don't hesitate to ask. Cheers, Russ Tyndall commit 6fe408e85926329de511cc533c3c670b802df641 Author: Russ Tyndall <russ(a)acceleration.net> Date: Mon May 2 16:07:32 2011 -0400 Refactored dom:map-document into methods of dom:walk * dom:map-document now calls dom:walk on the document * walk used to be a labels inside of map-document, now it is a generic function called by map-document commit 0af0575d47379505ee4b89d042d0c7929b6e727e Author: Russ Tyndall <russ(a)acceleration.net> Date: Mon May 2 16:06:44 2011 -0400 make cxml:attribute* helper accept and correctly set specified-p (which defaults to T rather than the previous nil) * specified-p determines whether or not an attribute is considered being a default attribute vs one that has been explicitly set. Since this is a builder function, it seems that this should be T by default.

1 0

[cxml-devel] roundtripping vcard-4.0 RNG schema
by Cyrus Harmon 28 Apr '11

28 Apr '11

So, I've been messing around with vcards a bit and decided that I would try to make sense of the new XML format for VCARD data, described here: http://tools.ietf.org/html/draft-perreault-vcarddav-vcardxml-02#appendix-A So far so good. I cut and paste the RNG spec from the document (attached), and attempt to read in the compact form and write out the longhand XML RNG schema. So, I do: (defparameter *compact* (cxml-rng:parse-compact #p"vcard-4_0.rng")) ;; so far so good (cxml-rng:make-validator *compact*) ;; again, that works (with-open-file (out "foo.xml" :direction :output :element-type '(unsigned-byte 8)) (cxml-rng:serialize-schema *compact* (cxml:make-octet-stream-sink out))) ;; BOOM! I get the following error: There is no applicable method for the generic function #<STANDARD-GENERIC-FUNCTION CXML:UNPARSE-ATTRIBUTE (3)> when called with arguments (#:ANONYMOUS2507). [Condition of type SIMPLE-ERROR] Restarts: 0: [RETRY] Retry calling the generic function. 1: [*ABORT] Return to SLIME's top level. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "worker" RUNNING {1002D97001}>) Backtrace: 0: ((SB-PCL::FAST-METHOD NO-APPLICABLE-METHOD (T)) #<unused argument> #<unused argument> #<STANDARD-GENERIC-FUNCTION CXML:UNPARSE-ATTRIBUTE (3)> #:ANONYMOUS2507) 1: (SB-PCL::CALL-NO-APPLICABLE-METHOD #<STANDARD-GENERIC-FUNCTION CXML:UNPARSE-ATTRIBUTE (3)> (#:ANONYMOUS2507)) 2: (CXML:ATTRIBUTE* #<unavailable argument> #<unavailable argument> #<unavailable argument> "name") Locals: CXML::LNAME = :<NOT-AVAILABLE> CXML::PREFIX = :<NOT-AVAILABLE> CXML::QNAME = "name" CXML::VALUE = :<NOT-AVAILABLE> 3: ((LAMBDA ())) 4: (CXML::INVOKE-WITH-ELEMENT* #<CLOSURE (LAMBDA #) {1002E13BA9}> #<unavailable argument> #<unavailable argument> "ref") Locals: CXML::FN = #<CLOSURE (LAMBDA ()) {1002E13BA9}> CXML::LNAME = :<NOT-AVAILABLE> CXML::PREFIX = :<NOT-AVAILABLE> CXML::QNAME = "ref" 5: (CXML-RNG::SERIALIZE-PATTERN #<CXML-RNG:REF {1006DB5171}>) 6: ((LAMBDA ())) 7: (CXML::INVOKE-WITH-ELEMENT* #<CLOSURE (LAMBDA #) {1002E13AF9}> #<unavailable argument> #<unavailable argument> "start") Locals: CXML::FN = #<CLOSURE (LAMBDA ()) {1002E13AF9}> CXML::LNAME = :<NOT-AVAILABLE> CXML::PREFIX = :<NOT-AVAILABLE> CXML::QNAME = "start" 8: ((LAMBDA ())) 9: (CXML::INVOKE-WITH-ELEMENT* #<CLOSURE (LAMBDA #) {1002E13A89}> #<unavailable argument> #<unavailable argument> "grammar") Now, normally, I'd just assume that this is something I messed up. But the fact that the schema parses and validates OK makes me wonder. Any suggestions on how to go about debugging this? thanks, Cyrus

1 2

[cxml-devel] ... and now for something completely different ...
by Marco Antoniotti 22 Apr '11

22 Apr '11

... and more interesting. I am past the set-up phase and I got to the point of building a SAX parser (I have not figured out yet what is the practical difference between SAX and StAX). My beef with XML is obviously increasing :) But let's not go there. Here is my thinking. I write SAX:START-ELEMENT methods and let each one of them look like (defmethod sax:start-element ((h smbl-handler) namespace-uri (local-name (equal "model")) qname attributes) ...) (defmethod sax:start-element ((h smbl-handler) namespace-uri (local-name (equal "compartment")) qname attributes) ...) You get the idea... Of course, we don't have EQUAL specializers (and I don't want to depend on "predicate dispatching" extensions :) ) so I did the following trick. (defclass sbml-parser (sax:sax-parser) ; Why do I need this? () ) (defclass sbml-handler (sax:default-handler) ((source :reader sbml-handler-source :initarg :source) (pathname :reader sbml-handler-pathname :initarg :pathname) ) ) (defclass sbml-symbolizer (cxml:sax-proxy) ()) ... and ... (defmethod sax:start-element ((h sbml-symbolizer) namespace-uri local-name qname attributes) (sax:start-element (cxml:proxy-chained-handler h) (intern namespace-uri) (intern local-name) (intern qname) attributes) ) So now I can write (defmethod sax:start-element ((h smbl-handler) (namespace-uri (eql '|http://www.smbl.org/sbml/level2/version4|)) (local-name (eql '|compartment|)) qname attributes) ...) apart from the details... Do you guys think this is a sensible approach? It'd make writing the SAX parser a cinch. Thanks -- Marco Antoniotti

1 0

[cxml-devel] ... and another
by Marco Antoniotti 22 Apr '11

22 Apr '11

Always on LWM. I assume this has to do with UNICODE or not support, but the example in the docs is misleading. CL-USER 37 > (defparameter *source* (cxml:make-source "<example>text</example>")) Error: In = of (#\< 254) arguments should be of type NUMBER. 1 (continue) Return a value to use. 2 Supply a new first argument. 3 (abort) Return to level 0. 4 Return to top loop level 0. Type :b for backtrace or :c <option number> to proceed. Type :bug-form "<subject>" for a bug report template or :? for other options. Cheers -- Marco Antoniotti

2 5

[cxml-devel] Counter-intuitive API for cxml:parse on LWM?
by Marco Antoniotti 21 Apr '11

21 Apr '11

Hi here is the example on LWM: CL-USER 17 > (cxml:parse #P"CellCycle-1991Tys-2.xml" (cxml:make-whitespace-normalizer (make-instance 'sax:default-handler)) :validate nil) NIL CL-USER 18 > (with-open-file (f #P"CellCycle-1991Tys-2.xml" :direction :input) (cxml:parse f (cxml:make-whitespace-normalizer (make-instance 'sax:default-handler)) :validate nil)) Error: Binary operation READ-BYTE attempted on character stream #<STREAM::LATIN-1-FILE-STREAM /Users/marcoxa/Projects/Genomics/biolosyst/sbmlambda/tests/CellCycle-1991Tys-2.xml>. 1 (abort) Return to level 0. 2 Return to top loop level 0. Type :b for backtrace or :c <option number> to proceed. Type :bug-form "<subject>" for a bug report template or :? for other options. CL-USER 19 : 1 > And here is the doc string for cxml:parse "@arg[input]{A string, pathname, octet vector, or stream.} @arg[handler]{A @class{SAX handler}} @arg[validate]{Boolean. Defaults to @code{nil}. If true, parse in validating mode, i.e. assert that the document contains a DOCTYPE declaration and conforms to the DTD declared.} ... @arg[recode]{Boolean. (Ignored on Lisps with Unicode support.) Recode rods to UTF-8 strings. Defaults to true. Make sure to use @fun{utf8-dom:make-dom-builder} if this option is enabled and @fun{rune-dom:make-dom-builder} otherwise.} @return{The value returned by @fun{sax:end-document} on @var{handler}.} Parse an XML document from @var{input}, which can be a string, pathname, octet vector, or stream. ... All SAX parsing functions share the same keyword arguments. Refer to @fun{parse} for details on keyword arguments." It appears that you need a 'xstream', but this is against the doc string content (and IMHO, against common sense). Cheers -- Marco Antoniotti

2 3

[cxml-devel] normalize-text-nodes!
by Andy Chambers 13 Jun '10

13 Jun '10

Hi, Using xuriella to perform the identity transform fails when there are empty elements (e.g. "<BasicDefinitions/>") in the source document. I believe the problem is in normalize-text-nodes! which doesn't check to see if there are any children before trying to iterate over them. This seems to trigger an assertion error in sbcl. XURIELLA> (apply-stylesheet #p"/usr/src/discworld/xslt/identity.xsl" "<root>abc</root>") "<?xml version=\"1.0\" encoding=\"UTF-8\"?> <root>abc</root>" XURIELLA> (apply-stylesheet #p"/usr/src/discworld/xslt/identity.xsl" "<root></root>") The value NIL is not of type VECTOR. [Condition of type TYPE-ERROR] Restarts: 0: [RETRY] Retry SLIME REPL evaluation request. 1: [ABORT] Return to SLIME's top level. 2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "repl-thread" RUNNING {CA2E459}>) Backtrace: 0: (CXML-STP-IMPL::NORMALIZE-TEXT-NODES! #.(CXML-STP:ELEMENT #| :PARENT of type DOCUMENT |# :LOCAL-NAME "root")) 1: ((SB-PCL::FAST-METHOD XPATH-PROTOCOL:CHILD-PIPE-USING-NAVIGATOR ((EQL :DEFAULT-NAVIGATOR) CXML-STP:ELEMENT)) ..) 2: ((LAMBDA (XPATH::NODE XPATH::STARTING-NODE)) #.(CXML-STP:ELEMENT #| :PARENT of type DOCUMENT |# :LOCAL-NAME "root") #.(CXML-STP:ELEMENT #| :PARENT of type DOCUMENT |# :LOCAL-NAME "root")) 3: ((LAMBDA (XPATH:CONTEXT)) #<XPATH:CONTEXT {C750F39}>) Simple fix is attached. Cheers, Andy

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cxml-devel