[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: RDDL API

• From: Michael Brennan <Michael_Brennan@A...>
• To: 'Jonathan Borden' <jborden@m...>, xml-dev@l...
• Date: Fri, 05 Jan 2001 13:11:22 -0800

I think I like the Resource interface approach.

> -----Original Message-----
> From: Jonathan Borden [mailto:jborden@m...]
> Sent: Thursday, January 04, 2001 9:04 PM
> To: Michael Brennan; xml-dev@l...
> 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
> 

• Follow-Ups:
  • RE: RDDL API
    • From: Jonathan Borden <jborden@m...>

• Prev by Date: RE: schemas: can I restrict an elem's content based on att value
• Next by Date: RE: Resource Gloss (Human Readable)
• Previous by thread: RE: RDDL API
• Next by thread: RE: RDDL API
• Index(es):
  • Date
  • Thread