Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] Validating Against Relax NG Schemas?

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Randall R Schulz <rschulz AT sonic.net>
  • To: xom-interest AT lists.ibiblio.org
  • Subject: Re: [XOM-interest] Validating Against Relax NG Schemas?
  • Date: Wed, 25 Oct 2006 12:21:41 -0700

Wolfgang,

On Wednesday 25 October 2006 11:52, Wolfgang Hoschek wrote:
> ...
> >
> > By the way, perhaps I should mention that I plan to use eXist for
> > XML persistence in the system I'm building.
>
> From a XOM perspective, Nux adds features on top of XOM. Basically,
> I'd recommend to use plain XOM where that's sufficient and pull in
> those add-on features where they seem to have enough value for
> whatever problem you may have at hand.
>
> ...
>
> XOM is a main-memory XML model and can't be made persistent. I think
> the eXist database doesn't know anything about XOM, so for getting
> data in and out of eXist you'll probably wind up not using XOM at
> all, or converting XOM to and from some standard such as SAX, DOM or
> StaX.


I plan to use eXist as a free-standing service, not as a library
component linked directly to my code. Thus I will interact with it
using XML in text form and that is why I require XML handling to link
into my existing code at the edges.

[
Further background:

I already have a large library of Java types that are to be made
persistent in XML using eXist, and my intention is to use XOM (or Nux)
in the conversion between those internal types and XML equivalents.

The source of the information represented by these internal types is a
variety of human-oriented logic languages (KIF and the TPTP problem
format, e.g.). The internal data structures are used by theorem-proving
and logic programming algorithms. The purpose for the XML repository is
largely to add support for creating human-interfaces for building and
managing theory libraries and knowledge bases. So while there's a
single internal representation for the formulas, there are several
external ones, XML being the newest.

I might add that building Web interfaces using JSP and custom tags, (my
first attempt) is much too tedious for my taste and still doesn't
address content persistence. Using XML and its toolset gives me a huge
leg up in persistence, content management and Web-based UI
construction.
]


Randall Schulz




Archive powered by MHonArc 2.6.24.

Top of Page