cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Davanum Srinivas <d...@yahoo.com>
Subject Re: proposal: entity resolution capability
Date Tue, 21 Aug 2001 11:26:37 GMT
David,

Looking forward to your sample catalog demo, docs etc. Please let us know if you run into
trouble.
Once you are done, please post a zip file that contains.
- Any new files with suggested directory structure.
- Run "cvs diff -u" from the main directory and add the output as a diff file.

For default config, you can borrow code from FOPSerializer, search for "user-config" keyword.
FOPSerializer can load user configuration from an external xml file.

Thanks,
dims

--- David Crossley <crossley@indexgeo.com.au> wrote:
> On Mon, 20 Aug 2001, dims wrote:
> > David,
> > Please look into the latest C2.1, I have added some support
> > for Catalogs. See my commit message extract below. I used
> > Norman Walsh's classes as the default since i have no idea
> > about license for your classes etc.
> 
> That is brilliant Dims. I removed our old test catalog
> support, did cvs checkout 2.1-dev of your new stuff, and
> added a properties file. Everything works as expected. Great.
> 
> It does not matter now, but the catalog classes that we had
> used for the proposal were also Sun's by Norm Walsh which
> he made available via Arbortext. (We were not doing anything
> special - just hooking the classes up to the parser's entity
> resolver via JaxpParser.java and XercesParser.java)
> 
> The new SUN classes would have evolved from those. These are
> current and form a better base. The way that you have
> implemented it is also far better than our original proposal.
> Well done. (Where do you get the time :-)
> 
> I will separately send the sample catalog demo that i had
> prepared for our original proposal, together with our initial
> properties file, a default catalog, and a default set of ISO
> character entity sets. I will then re-work our proposal
> documentation catalog.xml to become the user doco.
> 
> We can now build upon your solid base. I will follow up
> separately with a couple of issues, e.g default config.
> 
> many thanks, David Crossley
> 
> On Mon, 20 Aug 2001, dims continued:
> > 
> > ----------------------------------------------------------------------
> > This is the initial commit for support for
> > Catalogs for Entity Resolution.
> > - Uses the XML Entity and URI Resolvers Java [tm] classes at
> > http://www.sun.com/xml/developers/resolver/
> > - The spec for catalogs are at
> > http://www.oasis-open.org/committees/entity/spec.html
> > - Componentized such that others (like the folks at
> > www.indexgeo.com.au/work/cocoon/catalog.html)
> > can use their own catalog components.
> > 
> > Needs more work:
> > - Add sample CatalogManager.properties file
> > - Samples to show Entity Resolution at work.
> > - Updates to the Documentation.
> > - etc, etc...
> > ----------------------------------------------------------------------
> > 
> > Thanks,
> > dims
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 


=====
Davanum Srinivas, JNI-FAQ Manager
http://www.jGuru.com/faq/JNI

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message