--- In dita-users@yahoogroups.com, "Ricardo Mattiazzi" <ladraum@...>
wrote:
> Im using the full path because someone sugested me to do it, to make it
> easier to use XMetaL and DITA-OT. I think that the paths should be
relative,
> but how can i make it work with the catalog ?

You could do this for a proof of concept. If it works you can tidy it
up later as a DITA-OT plugin.

Invent a public ID (a character string) that no one else has used.
It's customary to put your company name in it somewhere.
-//Moldflow//DTD DITA MyInfoType//EN
-//Moldflow//ELEMENTS DITA MyInfoType//EN
Look in catalog-dita.xml for examples you could copy.

Add extra entries into the catalog-dita.xml file so that they point to
your file. Use URLs (forward slashes) relative to the DITA Open
Toolkit directory. (Note: catalog-dita.xml is a generated file. It
is overwritten when you run the "integrator" task. If you find your
changes are being removed, put them in catalog-dita_template.xml instead.)

Put your DTDs (.dtd and .mod) in the place that the catalog file
points to.

Make your .dtd file refer to your .mod file using a PUBLIC entity.
Instead of
<!ENTITY %
introducao-typemod
SYSTEM
"..." >
say
<!ENTITY %
introducao-typemod
PUBLIC
"-//Moldflow//ELEMENTS DITA MyInfoType//EN"
"The system ID is ignored but must be present" >
Again, look at the examples in other .dtd files.

Now your specializations ought to be as authentic as any other DITA
topic type. See if they work.