OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: RDDL API



I think I like the Resource interface approach.

> -----Original Message-----
> From: Jonathan Borden [mailto:jborden@mediaone.net]
> Sent: Thursday, January 04, 2001 9:04 PM
> To: Michael Brennan; xml-dev@lists.xml.org
> Subject: RE: RDDL API
> 
> 
> Michael Brennan wrote:
> >
> >
> > What about having the "getResource" return a 
> javax.activation.DataSource
> > object rather than an InputStream? That way the content-type can
> > be conveyed
> > if it is defined in the catalog.
> >
> 
> 	That would be good, though to maximize portability e.g. 
> JDK 1.1 etc, would
> it be better to do:
> 
> 	URLConnection getConnection(String namespaceURI,String arcrole);
> 
> Alternatively define a Resource class:
> 
> package org.rddl;
> 
> interface Resource {
> 	String getURI();
> 	String getHref();
> 	String getArcrole();
> 	String getRole();
> 	String getContentType();
> 	InputStream getInputStream();
> 	URLConnection getConnection();
> }
> class RDDLFilter extends SAX2Filter {
> 	Resource getResource(String arcroleURI);
> 	void parse(String namespaceURI);
> };
> 
> -Jonathan
>