And emacs seems to lack XML related tools, because there are no good elisps to deal with even XSLT.
- Here, how to use Saxon on cui to run the examples in the book.
bash-3.2$ java -cp ~/Dropbox/java/lib/saxon9he.jar net.sf.saxon.Transform -t -s:02-01.xml -xsl:02-03.xsl
Saxon-HE 9.3.0.4J from Saxonica
Java version 1.6.0_24
Warning: at xsl:stylesheet on line 2 column 80 of 02-03.xsl:
Running an XSLT 1 stylesheet with an XSLT 2 processor
Stylesheet compilation time: 3222 milliseconds
Processing file:/Volumes/Macintosh%20HD2/Dropbox/programming/xml-visual-quickstart-guide/Chapter_02_examples/02-01.xml
Using parser com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser
Building tree for file:/Volumes/Macintosh%20HD2/Dropbox/programming/xml-visual-quickstart-guide/Chapter_02_examples/02-01.xml using class net.sf.saxon.tree.tiny.TinyBuilder
Tree built in 1 milliseconds
Tree size: 16 nodes, 32 characters, 1 attributes
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Wonders of the World</title>
</head>
<body>
<h1>Wonders of the World</h1>
The Colossus of Rhodes
is located in Rhodes, Greece.
</body>
</html>Execution time: 320ms
Memory used: 21579320
NamePool contents: 19 entries in 19 chains. 6 prefixes, 6 URIs
bash-3.2$ - Hum, XSLT files are in the end XML files, and it must be well-formed. That kind of restriction must be not adequate as a template language.
- As the content of sample xml files, ancient wonders are boring. So I'd better create my examples.
- I've thought about which kind of data I should deal with as my own examples, and I realized that the address data would be fine with me. I'll adopt vCard objects in RDF as the xml vocabulary. [Representing vCard Objects in RDF]
And you can also check what the vCard data in the wild are in my wiki entry. [aka:アドレス帳]
0 件のコメント:
コメントを投稿