The short answer is yes, oXygen uses XML Catalogs to resolve schema and
DTD URLs that it knows about. The root catalog lives in
frameworks/catalogs.xml in the directory or folder where oXygen is
installed. The file frameworks/tei/xml/tei/custom/schema/catalog.xml
contains the rewrites that are done on URLs corresponding to the TEI
schemas.
I don't believe that there is a way to prevent this from happening other
than by deleting or renaming the catalog file, in which case oXygen will
use the URL to retrieve the schema from the Internet.
Because the schema files distributed with oXygen sometimes lag behind
the latest TEI releases, kind souls like Syd Bauman have from time to
time packaged new schema files so that they can be unpacked to replace
part of the oXygen frameworks hierarchy. You could also go to
http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/
and grab the files there to replace the ones in a local oXygen
directory.
On Fri, 11 Apr 2008, Dan O'Donnell wrote:
> Hi all,
>
> I have a question that maybe those who use Oxygen can answer.
>
> I've associated a document with
> http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng
> within Oxygen.
>
> It is gagging at @when within date claiming it ain't permitted, when a
> glance at the schema shows that it is.
>
> Does anybody know if some kind of substitution happens? I.e. could
> Oxygen be using an internal version of tei_all, even though the
> <?oxygen> tag is pointing at a URL?
>
> -dan
>
--
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 801079, Charlottesville, VA 22904-4318 USA
Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
Email: [log in to unmask] Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/
|