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

[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