Jonathan Borden wrote: > Is this so odd, I think we should try to leverage the naming and resource > identification facilities of URIs XLink and XPointer.
It's not odd, but it's also not really acceptable in situations where a data source can't be represented as a URI. Example: Pure Oracle connection data (not aliases) can't be easily represented as a URI, so by saying that the source be anything implementor specific, you allow for every possible wacky address. Then, if we want to implement our own products using a URI pattern, then so be it. I just don't think it should be a requirement. --Tom -- <name>Tom Bradford</name> <title>Chief Software Architect</title> <company>The dbXML Group</company> <phone>(480) 421-1233</phone> ------------------------------------------------------------------ Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://www.xmldb.org/ ------------------------------------------------------------------
