Package: wap-wml-tools Version: 0.0.4-1 Severity: minor File: /usr/bin/rdfwml
On java.net rdf feed, I found an HTML Entity declared externally, but it
causes rdfwml to break:
|> rdfwml broken.rdf
|broken.rdf:101: error: Entity 'uuml' not defined
| eads to the question of where to store and how to load this code. Thomas
Kü
^
|Couldn't parse broken.rdf as a valid XML document
Attached is the full RDF from
http://today.java.net/pub/q/articles_rss?x-ver=1.0
If I delete the ü or change it into a char entity, it works.
I think this is due to the fact, that the external entities are declared,
but not used (%HTMLlat1;). However if I use it like this:
<?xml version="1.0"?>
<!DOCTYPE rdf:RDF [
<!ENTITY % HTMLlat1 PUBLIC
"-//W3C//ENTITIES Latin 1 for XHTML//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent";>
%HTMLlat1;
]>
then rdfwml does not produce any usefull output:
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
"http://www.wapforum.org/DTD/wml_1.1.xml";>
<wml>
<template>
<do type="accept" label="Back">
<prev/>
</do>
</template>
<card id="init" title="Headlines">
</card>
</wml>
Gruss
Bernd
<?xml version="1.0"?>
<!DOCTYPE rdf:RDF [
<!ENTITY % HTMLlat1 PUBLIC
"-//W3C//ENTITIES Latin 1 for XHTML//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent";>
]>
<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#";
xmlns:dc="http://purl.org/dc/elements/1.1/";
xmlns:on="http://www.oreillynet.com/csrss/";
xmlns="http://purl.org/rss/1.0/";
>
<channel rdf:about="http://www.java.net/pub/q/articles";>
<title>java.net Articles</title>
<link>http://www.java.net/pub/q/articles</link>
<description>
Latest java.net articles
</description>
<dc:rights>Copyright 1995-2003, Sun Microsystems, Inc</dc:rights>
<dc:publisher>[EMAIL PROTECTED] (Daniel Steinberg)</dc:publisher>
<dc:language>en-us</dc:language>
<items>
<rdf:Seq>
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/05/05/packageSQ4.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/05/03/midletUI.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/04/28/soadesign.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/04/26/extending.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/04/21/farm.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/04/19/desktoplive.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/04/14/dependency.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/04/11/twain.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/04/07/pojostrategy.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/04/01/fools.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/03/29/webwizard2.htm"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/03/24/autoboxing.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/03/22/laszlo.html"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/03/15/webwizard1.htm"; />
<rdf:li
rdf:resource="http://today.java.net/pub/a/today/2005/03/09/factory.html"; />
</rdf:Seq>
</items>
</channel>
<item rdf:about="http://today.java.net/pub/a/today/2005/05/05/packageSQ4.html";>
<title>(Not So) Stupid Questions 4: Assigning Packages</title>
<link>http://today.java.net/pub/a/today/2005/05/05/packageSQ4.html</link>
<description>
This "stupid question" is about how to best organize your classes
in packages.
</description>
<dc:creator></dc:creator>
<dc:subject>Programming</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-05-05</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:tile>http://today.java.net/images/tiles/111-stupid_q.gif</on:tile>
<on:short_desc>Building packages and subpackages</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/05/03/midletUI.html";>
<title>J2ME Tutorial, Part 2: User Interfaces with MIDP 2.0</title>
<link>http://today.java.net/pub/a/today/2005/05/03/midletUI.html</link>
<description>
In part two of the J2ME tutorial you will create the user interface (UI)
elements of a MIDlet. Since the interaction with a user is a paramount concern
in any MIDlet, due to the size of the screens, it is important for you to
understand the basics of this side of MIDlets. Any interaction with a user is
done via a UI element.
</description>
<dc:creator>Vikram Goyal</dc:creator>
<dc:subject></dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-05-03</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>179</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-j2me_tutorial.gif</on:tile>
<on:short_desc>User interfaces with MIDP 2.0</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/04/28/soadesign.html";>
<title>Designing an Enterprise Application Framework for Service-Oriented
Architecture</title>
<link>http://today.java.net/pub/a/today/2005/04/28/soadesign.html</link>
<description>
It's one thing to talk about the advantages of a service-oriented
architecture, and another to drill down to a design that satisfies the needs of
an SOA framework. In this article, Shyam Kumar Doddavula and Sandeep
Karamongikar spell out just how such a framework can be put together.
</description>
<dc:creator>Shyam Kumar Doddavula, Sandeep Karamongikar</dc:creator>
<dc:subject></dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-04-28</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>314313</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-service_architecture.gif</on:tile>
<on:short_desc>How to build a service-oriented architecture</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/04/26/extending.html";>
<title>The Java Extension Mechanism</title>
<link>http://today.java.net/pub/a/today/2005/04/26/extending.html</link>
<description>
Java has a huge collection of classes, but many projects need to call upon
code outside of core Java, which leads to the question of where to store and
how to load this code. Thomas Künneth shows how Java's Extension Mechanism
allows you to make new code available to all Java applications.
</description>
<dc:creator>Thomas Künneth</dc:creator>
<dc:subject>Programming</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-04-26</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>155</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-extension_mech.gif</on:tile>
<on:short_desc>Exposing your classes to multiple JVMs</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/04/21/farm.html";>
<title>How To Build a ComputeFarm</title>
<link>http://today.java.net/pub/a/today/2005/04/21/farm.html</link>
<description>
Parallel computing allows some programs to run faster by dividing them up
into smaller pieces and running these pieces on multiple processors.
ComputeFarm is an open source Java framework for developing and running
parallel programs.
</description>
<dc:creator>Tom White</dc:creator>
<dc:subject></dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-04-21</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>294</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-computefarm.gif</on:tile>
<on:short_desc>How to build a ComputeFarm</on:short_desc>
</item>
<item
rdf:about="http://today.java.net/pub/a/today/2005/04/19/desktoplive.html";>
<title>Swing Threading</title>
<link>http://today.java.net/pub/a/today/2005/04/19/desktoplive.html</link>
<description>
In this excerpt from SourceBeat's <i>Java Desktop Live</i>,
Scott Delap begins by giving you an up-close look at the event dispatch thread
(EDT), which is responsible for dispatching events to the appropriate Swing
component and for performing the paint operations of Swing components. It
doesn't take long for even experienced programmers to lock up the user
interface or dramatically slow down the responsiveness of a Swing application.
This excerpt takes a close look at the Swing threading model and provides
advice and examples for getting the most out of your Swing application.
</description>
<dc:creator>Scott Delap</dc:creator>
<dc:subject></dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-04-19</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>312</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-swing_thread_xcrpt.gif</on:tile>
<on:short_desc><i>Java Desktop Live</i> excerpt: Swing
threading</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/04/14/dependency.html";>
<title>Breaking the Last Dependency</title>
<link>http://today.java.net/pub/a/today/2005/04/14/dependency.html</link>
<description>
All of the factory patterns "encapsulate" the instantiation of
concrete classes and help to minimize (as well as localize) the dependencies
your code has on those concrete classes. This articles explains what
"breaking the last dependency" means, how it relates to the Factory
pattern, and why you should care.
</description>
<dc:creator>Elisabeth Freeman, Eric Freeman</dc:creator>
<dc:subject></dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-04-14</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>234</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-break_depends.gif</on:tile>
<on:short_desc>Breaking the last dependency</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/04/11/twain.html";>
<title>Java Tech: Acquire Images with TWAIN and SANE, Part 3</title>
<link>http://today.java.net/pub/a/today/2005/04/11/twain.html</link>
<description>
TWAIN is the standard for image acquisition from scanners and digital
cameras, but its GUI assumptions make it ill-suited for Linux and other *nix
operating systems. In part three of his series looking at image acquisition in
Java, Jeff Friesen looks at the SANE alternative, and how to use it with Java.
</description>
<dc:creator>Jeff Friesen</dc:creator>
<dc:subject>Programming</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-04-11</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>174</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-javatech.gif</on:tile>
<on:short_desc>Explore the SANE alternative to TWAIN</on:short_desc>
</item>
<item
rdf:about="http://today.java.net/pub/a/today/2005/04/07/pojostrategy.html";>
<title>Using the Strategy Design Pattern for Sorting POJOs</title>
<link>http://today.java.net/pub/a/today/2005/04/07/pojostrategy.html</link>
<description>
You have some plain ol' Java objects and you want to sort them. By what
field? Well, by which ever one the user wants. But that implies different kinds
of search logic, and how will you keep it straight? Olexiy Prohorenko shows how
the Strategy design pattern is perfectly suited to solve this problem.
</description>
<dc:creator>Olexiy Prohorenko</dc:creator>
<dc:subject>Patterns</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-04-07</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>269</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-strategy_pattern.gif</on:tile>
<on:short_desc>Sorting with swappable strategies</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/04/01/fools.html";>
<title>April Fools 2005</title>
<link>http://today.java.net/pub/a/today/2005/04/01/fools.html</link>
<description>
What Java/technology April Fools stories would you have run this year?
</description>
<dc:creator>Daniel H. Steinberg</dc:creator>
<dc:subject>Community</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-04-01</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>23</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-april.gif</on:tile>
<on:short_desc>April Fools 2005</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/03/29/webwizard2.htm";>
<title>Web Wizard Component, Part 2: The View</title>
<link>http://today.java.net/pub/a/today/2005/03/29/webwizard2.htm</link>
<description>
A GUI wizard is something that's surprisingly tricky to get right in a web
application. In the conclusion of this series, Michael Jouravlev takes the
model from part one and builds out the user interface with Struts, addressing
some interesting web usability problems along the way.
</description>
<dc:creator>Michael Jouravlev</dc:creator>
<dc:subject>Programming, Struts</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-03-29</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>298</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-web_wiz.gif</on:tile>
<on:short_desc>Creating the web-based wizard UI</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/03/24/autoboxing.html";>
<title>Boxing Conversion in J2SE 5.0</title>
<link>http://today.java.net/pub/a/today/2005/03/24/autoboxing.html</link>
<description>
J2SE 5.0's autoboxing feature liberates you from the hassle of bundling
your primitives into wrapper objects in various situations (like putting them
in collections), but autoboxing doesn't always behave as you might expect.
Krishna Srinivasan has details on how this milestone feature really works.
</description>
<dc:creator>Krishna Srinivasan</dc:creator>
<dc:subject>Programming</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-03-24</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>306</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-autoboxing.gif</on:tile>
<on:short_desc>What's in the box might surprise you</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/03/22/laszlo.html";>
<title>Laszlo: An Open Source Framework for Rich Internet
Applications</title>
<link>http://today.java.net/pub/a/today/2005/03/22/laszlo.html</link>
<description>
William Grosso gives you a quick overview of Laszlo, an open source rich
internet applications development platform. After a high-level overview of what
Laszlo is and how it works, you'll get a quick tour through some of the basic
features of Laszlo, and see what's involved in building a very application in
Laszlo. Finally, he looks at where it does and does not make sense to use
Laszlo.
</description>
<dc:creator>William Grosso</dc:creator>
<dc:subject>Databases</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-03-22</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>57</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-explorations.gif</on:tile>
<on:short_desc>An open source framework for rich internet
applications</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/03/15/webwizard1.htm";>
<title>Web Wizard Component, Part 1: The Model</title>
<link>http://today.java.net/pub/a/today/2005/03/15/webwizard1.htm</link>
<description>
A GUI wizard is something that's surprisingly tricky to get right in a web
application. In this first article of a two-part series, Michael Jouravlev
shows how to build a suitable data model for managing the wizard behavior from
the server side.
</description>
<dc:creator>Michael Jouravlev</dc:creator>
<dc:subject>Programming, Struts</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-03-15</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>298</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-web_wiz.gif</on:tile>
<on:short_desc>Taking the wizard from the desktop to the web
app</on:short_desc>
</item>
<item rdf:about="http://today.java.net/pub/a/today/2005/03/09/factory.html";>
<title>Principles, Patterns, and Practices: The Factory Pattern</title>
<link>http://today.java.net/pub/a/today/2005/03/09/factory.html</link>
<description>
There are several design patterns allow us to hide the type of an object
even from those who seek to create it. These patterns are known as
<i>Factories</i>.
</description>
<dc:creator>Robert C. Martin</dc:creator>
<dc:subject>Patterns</dc:subject>
<dc:language>en-us</dc:language>
<dc:date>2005-03-09</dc:date>
<dc:format>text/html</dc:format>
<dc:rights>Copyright 2005, Sun Microsystems, Inc.</dc:rights>
<dc:publisher>O'Reilly and Associates</dc:publisher>
<on:author_id>90</on:author_id>
<on:tile>http://today.java.net/images/tiles/111-design_patterns.gif</on:tile>
<on:short_desc>The Factory pattern</on:short_desc>
</item>
</rdf:RDF>
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Versions of packages wap-wml-tools depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libxml1 1:1.8.17-10 GNOME XML library
ii zlib1g [libz1] 1:1.2.2-3 compression library - runtime
-- no debconf information
broken2.rdf
Description: application/rdf
