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

 


Help: OASIS Mailing Lists Help | MarkMail Help

entity-resolution message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: SAX 2.0 enhancement proposal


/ Rob Lugt <roblugt@elcel.com> was heard to say:
| interface EntityResolver
| {
|     public InputSource resolveEntity(java.lang.String name,
|                                                          java.lang.String
| publicId,
|                                                          java.lang.String
| systemId,
|                                                          java.lang.String
| baseUri)
|     throws SAXException, java.io.IOException;
| }
| 
| This would give the EntityResolver everything it needs to do the job.  If it
| wanted to absolutize the system identifier then it could do so, but it would
| also have access to the bare value.

I agree wholeheartedly and I will say so when your message turns up on
xml-dev.

                                        Be seeing you,
                                          norm

-- 
Norman.Walsh@Sun.COM   | Our life gets as complicated as a comedy as it
XML Standards Engineer | goes on, but the complications get gradually
Technology Dev. Group  | resolved: see that the curtain comes down on a
Sun Microsystems, Inc. | good denouement.--Graci\'an


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC