[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: Thu, 04 Jan 2001 12:59:30 -0800

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.

> -----Original Message-----
> From: Jonathan Borden [mailto:jborden@m...]
> Sent: Wednesday, January 03, 2001 7:24 PM
> To: xml-dev@l...
> Subject: RDDL API
> 
> 
> I think it would be fairly straightforward to write a SAX 
> filter looking
> something like:
> 
>     RDDLFilter rdf .... oops can't use that name....
> 
>     RDDLParser rdp = new RDDLParser();
> 
>     ContentHandler ch = (ContentHandler) rdp;
> 
>     // hook it up...
> 
>     rdp.resolve(namespaceURI, arcroleURI);
> 
> 
>     This would work for well-formed resources and perhaps we 
> need something
> like
> 
>     InputStream s = rdp.getResource(namespaceURI,arcroleURI);
> 
>     for non-XML resources.
> 
>     Anything else needed?
> 
> -Jonathan
> 
> 

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

• Prev by Date: RE: XHTML m12n XSD
• Next by Date: Re: XHTML m12n XSD
• Previous by thread: RDDL API
• Next by thread: RE: RDDL API
• Index(es):
  • Date
  • Thread