Using the XML Catalog sounds ok as long as it supports both local and public ids. Ideally the catalog would just have an optional field/property for the display CSS, or maybe there could be a convention where the .css has to be in the same directory and have the same name as the .dtd. The editor needs to be able to find which dtd and css to use just by looking at the first few lines of the file being edited.
-----Original Message-----
From: David Carver [mailto:d_a_carver@xxxxxxxxx]
Sent: Tuesday, October 14, 2008 3:42 PM
To: WTP Incubator Dev list; Ed Burnette
Subject: VEX DTD/Schema Registration
Ed, you mentioned that we should take a look at possibly not requiring
the VEX Plugin Project to be created to hold the DTD and CSS
stylesheets. That the user should be able to do this with out having
to go through this process. A thought would be to leverage if possible
the XML Catalog provided by WTP as a possible list of available content
models to be used (either DTD or Schemas). As for registering the CSS,
we should probably provide a configuration preference page for
registering the CSS stylesheets to be used.
You've used VEX more to help write some of your books, so any input you
have would be appreciated. The code is checked in and there is now a
special component in the WTP Incubator bugzilla for reporting these issues.
Dave