#12 New resolver entry point

closed-wont-fix
nobody
5
2002-01-10
2001-12-22
No

In the discussion that followed RFE #434478, I think we
arrived at an improved API for resolving external
identifiers in XML:

resolveEntity2(name, publicId, baseURI, systemId)

I'd like to suggest that a resolveURI() entry point is
also needed at the SAX level:

resolveURI(baseURI, uri)

This is very similar to the URIResolver() in
jaxp.transformer (in fact, I think it's the same).

However, I believe that the onset of schema validation
requires that this resolver be pushed down into the SAX
level.

In particular, I definitely want schema URIs to be
passed through the resolver, but I think it's abusive
to use resolveEntity or resolveEntity2 for this
purpose since those URIs are not XML external
identifiers (or, in fact, entities in any XML 1.0 sense).

Discussion

  • Anonymous - 2002-01-10
    • status: open --> closed-wont-fix
     
  • Anonymous - 2002-01-10

    Logged In: YES
    user_id=44117

    see my responses on the sax-devel list.

    Basically, as requested this is
    (a) specific to W3C schemas, which should be layered
    (b) not even necessary.

    It's not a good thing to expect that URIs being used
    in the context of external entity resolution get treated
    substantially differently from URIs used in any other
    context, and this RFE presumes that fostering such
    (confusing) actions is good.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks