cxml-devel

cxml-devel@common-lisp.net

167 discussions

[cxml-devel] Klacks bug with &# entities on CCL
by Andreas Fuchs 10 Sep '12

10 Sep '12

Hi there, The following code breaks in CCL (Version 1.8-r15286M (DarwinX8632)) with the most recent cxml from quicklisp (cxml-20110619-git): (klacks:with-open-source (source (cxml:make-source "<value> 987lkjasd</value>")) (klacks:consume source) (klacks:consume source) (klacks:consume source)) Here's the SLIME backtrace I get from evaluating that form: 0: ((SETF RUNES:%RUNE) #\ "" 0) 1: (CXML::READ-TOKEN-3 #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK ...)) 2: (CXML::PEEK-TOKEN #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK ...)) 3: (CXML::KLACKS/CONTENT #<CXML::CXML-SOURCE #xD7DE306> #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK ...) #<CCL:COMPILED-LEXICAL-CLOSURE (:INTERNAL ..)) 4: (CXML::KLACKS/ELEMENT-2 #<CXML::CXML-SOURCE #xD7DE306> #S(CXML::ZSTREAM :TOKEN-CATEGORY NIL :TOKEN-SEMANTIC NIL :INPUT-STACK ...) (("") ("xmlns" . "http://www.w3.org/2000/xmlns/") ..) #<CCL:COMPILED-L.. 5: (CXML::FILL-SOURCE #<CXML::CXML-SOURCE #xD7DE306>) 6: (#<STANDARD-METHOD KLACKS:CONSUME (CXML::CXML-SOURCE)> #<CXML::CXML-SOURCE #xD7DE306>) 7: (#<Anonymous Function #xD7E474E>) 8: (CCL::CHEAP-EVAL (KLACKS:WITH-OPEN-SOURCE (SOURCE (MAKE-SOURCE "<value> 987lkjasd</value>")) (KLACKS:CONSUME SOURCE) (KLACKS:CONSUME SOURCE) (KLACKS:CONSUME SOURCE))) That same form works on SBCL, so I assume there's some implementation-specific charset-related weirdness going on. I'm happy to help debug this, but sadly, my code-diving time is a bit limited at the moment. All the best, -- Andreas Fuchs, (http://|im:asf@|mailto:asf@)boinkor.net, antifuchs

1 0

[cxml-devel] Bug in DTD parsing?
by Bart Botta 29 Aug '12

29 Aug '12

(flex:with-input-from-sequence (s (babel:string-to-octets "<![IGNORE[ ]]>" :encoding :utf-8)) (cxml:parse-dtd-stream s)) errors with Document not well-formed: Unexpected character #\!. Context: Line 1, column 17 in NIL [Condition of type CXML:WELL-FORMEDNESS-VIOLATION] but parses OK with whitespace between ]]> and <!-- (for a real example, see line 396 in http://docbook.org/xml/4.3/dbpoolx.mod) it looks like P/IGNORE-SECT in cxml/xml/xml-parse.lisp should unread 1 rune after matching ]]> (or exit the loop sooner so it doesn't read an extra).

1 0

[cxml-devel] validating XML: document
by Alexandre Rademaker 12 Jul '12

12 Jul '12

Hello, I need to validate a XML file that doesn't have the doctype declaration. Actually, I don't control how the XML files are created so I am not able to change the fact that those files don't have doctype declarations. My problem is how to validate does files agains a DTD. I found at http://common-lisp.net/project/cxml/sax.html#parser that the correctly way should be: > (let ((d (cxml:parse-file "0675365413696898.xml" (cxml-dom:make-dom-builder))) (x (cxml:parse-dtd-file "LMPLCurriculo.DTD"))) (dom:map-document (cxml:make-validator x #"CURRICULO-VITAE") d)) But that gives me two warnings and return a NIL Warning: deprecated SAX default method used by a handler that is not a subclass of SAX:ABSTRACT-HANDLER or HAX:ABSTRACT-HANDLER Warning: deprecated SAX default method used by a handler that is not a subclass of SAX:ABSTRACT-HANDLER or HAX:ABSTRACT-HANDLER NIL It seems to work. I also tried with an invalid XML and the code fired an error! Nevertheless, what are bothering me are does warnings!! Any idea? Best, Alexandre Rademaker http://arademaker.github.com/

2 3

[cxml-devel] Inconsistency in creating %children vector
by Raymond Wiker 09 Jul '12

09 Jul '12

I was scratching my head for a couple of hours today, because of an apparent failure of cxml-dom::make-space - it did not increase the size of the %children vector. On closer examination, it turned out that the reason was that the %children vector was not adjustable, at that point. The only places in cxml-stp where %children is set up are in %unchecked-insert-child (parent-node.lisp) and normalize-text-nodes! in xpath.lisp. The first of these has (make-array ... :adjustable t ...), while the other does not. My guess is that normalize-text-nodes! might be called as part of an xpath evaluation, and if this happens in code that is actually building the cxml-stp structure, the result might be a situation where the %children vector is not adjustable. I'm not sure if this is a valid use of cxml-stp/xpath, but there is at least one documented case where it has been done :-) I could (trivially) change my code to not use xpath as part of the construction process, but adding :adjustable t to the call to make-array in xpath.lisp makes my (current) code work, and I guess it also makes cxml-stp slightly more robust.

1 0

[cxml-devel] Real-world example: with attachment
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

2 2

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

11 Jun '12

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cxml-devel