|
|
 top
|
  Subject: How does StylusStudio use OASIS Catalog document
Author: Tony Lavinio
Date: 04 Oct 2004 02:01 AM
|
Q1. is it necessary to always add the BaseCatalog to a project, in order to load the links to the Oasis Catalog XSD, etc?
A1. No. You can add any OASIS catalogs to the project, and they will be searched in the order listed. We provide the BaseCatalog functionality as a convenience.
Q2. it appears that the internal validator simply invokes an associated catalog automatically, or is a [nextCatalog] element added somewhere (where?) when you add a catalog to a project
A2. The internal validator will respect any catalogs in the project, and if they have nextCatalog links, those will be followed. We don't hide anything; there are no hidden catalogs. Only the ones you put in the project, and any that those delegate to, are searched.
Q3. Judging from the error messages, it does not appear that the external validators use the catalogs associate with a project.
Does this require extra arguments in the Options for Custom Validation Engines?
How can this be done?
A3. Only the built-in processors and validators can use these catalogs. There is no unified way or standard mechanism for plugging in custom uri resolvers that we can use to inform an arbitrary external validator of the catalogs available. However, if you know that you are using a specific catalog with a specific validator that supports catalogs, you can add a new custom engine which wraps the necessary options together, and call it as one of the built-in ones is called.
|
|
|
|
next