AFAIK, SYSTEM in XML is only "supposed" to be an URI, and does not necesarily need to be some accessible HTTP URL - it may point to the document autor's system and may not make sence in user's system. PUBLIC is what editors etc should map to their DTD repository.
There's also some discussion which seems trustworthy: http://bytes.com/forum/thread87407.html So you can have: <!DOCTYPE sqlMap PUBLIC "-//iBATIS.com//DTD SQL Map 2.0//EN" "~/ibatis/dtd/20.dtd"> where "~/ibatis/dtd/20.dtd" is the SYSTEM part. Whether or not the editors and clients rely on SYSTEM part instead of PUBLIC, is other topic. But for convenience, I would keep it be an URL :-) Ondra Clinton Begin wrote: > > It is a namespace, but also happens to map to a physical location on the > web, and thus there is the dependency. > > What I think would be better is a relative path scheme for DTDs, which > more > often than not would just be the same path that the XML file is in, but > would also allow developers to design their own structure. At the very > least would provide repository options other than an online resource that > eventually becomes a single point of inflexibility (and in some cases > failure). > -- View this message in context: http://www.nabble.com/Setting-for-removing-newlines-from-SQL--tp18916746p18974535.html Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
