[tssg-tech] Re: Parsing BostonEventsList with ROME
- From: Julie Carwellos <jcarwellos@xxxxxxxxx>
- To: tssg-tech@xxxxxxxxxxxxx
- Date: Fri, 24 Sep 2010 11:13:01 -0700 (PDT)
Harry, you're right. We have an n-tiered app here - lots and lots of
capabilities to be included (Java, JavaScript, XML, HTML, and we'll come across
more, I'm sure). So it's important to be clear. The following might help, and
anyone should jump in if I don't get it quite right:
JDOM - Java's document object model for loading XML files so that app code can
then traverse the model and pick and choose and change the information as it
wants.
DOM - X/DHTML's document object model, for the same reason, but it's with
Javascript. In this case, the incoming file needs to be HTML (Xtended or
Dynamic, hence the XHTML or DHTML). PHP and Perl I think can access the DOM,
too. But Android gives you hooks to use Javascript in apps.
Namespace is actually an XML thing, and the WWW Consortium has you put all
kinds of special casing into your own namespace. That way, anyone could define
something like a "book.xml" file in any way they wanted to, and as long as the
xml referenced it's own namespace there'd be no confusion. In our case, if BEL
had it's own namespace for RSS extensions, it could break down the XML tags
into a much more granular level than the RSS standard defines (aka Extensions).
If we're planning on displaying each event separately in an Android Web View,
then each event has to become a valid HTML file, most of which is in the
Description tag, and we can wrap it with the required HEAD and BODY tags.
This brings up another issue - where's the CSS? I would think we'd need to
develop a mobile.css, much as BEL probably already has files for print.css and
for other devices.
-julie
Other related posts:
