Arbortext's Java Catalog Classes for Resolution of Public Identifiers

[ptc-953960]

Does anyone have the Java Catalog Classes for Resolution of Public
Identifiers? They were to be open source, but I am unable to find them.


advises:

[April 04, 2000] Arbortext Releases Java Catalog Classes for Resolution
of Public Identifiers. Arbortext, Inc., "a leading provider of
Extensible Markup Language (XML)-based e-Content software, announced
today the immediate availability of open source Java-based code to
support public identifier resolution in XML documents. This code will
enable XML processors to resolve public identifiers which increases the
flexibility and interoperability of XML documents. These Java classes
implement the OASIS Entity Management Catalog format [('OASIS Technical
Resolution 9401:1997 (Amendment 2 to TR 9401)')] as well as an XML
Catalog format for resolving XML public identifiers into accessible
files or resources on a user's system or throughout the Web. These
classes can easily be incorporated into most Java-based XML processors,
thereby giving the users of these processors all the benefits of public
identifier use. As XML processors incorporate this code, users will be
able to utilize public identifiers in XML documents with the confidence
that they will be able to move those documents from one system to
another and around the Web knowing that they will also be able to refer
to the appropriate external file or Web page. These classes can easily
be plugged into any SAX Parser." Available to everyone at no cost, these
Java classes can be immediately downloaded from the ArborText web site.
The distribution includes examples of Catalog support with both Xerces
and XT. For additional details, see the full text of the ArborText
announcement: "Arbortext Makes Java Catalog Classes Available For Use by
XML Processors. Open Source Code Enables XML Processors to Resolve
Public Identifiers."

The link: no longer resolves and I am
unable to find it within PTC's search engine.

I've logged a support call with PTC and am not sure when they might be
able to find and provide these classes. I'm hoping somebody out there
has these and would be willing to share them.

Thanks,

John
--



Oracle Email Signature Logo
John Laurence Poole | Principal Software Engineer | 650.607.0853
Oracle User Assistance Engineering
M/S 2op1070
500 Oracle Parkway
Redwood Shores CA 94065-1677

Oracle Instant Chat: john.poole

The statements and opinions expressed here are my own and do
not necessarily represent those of Oracle Corporation.

[PaulGrosso]

See

[ptc-953960]

It looks like we are caught between two standards: the older "TR 9401
Catalog" standard and the more recent "XML Catalog" standard.

My predicament is this: we designed our DITA schemas using the Arbortext
catalog model (TR 9401).
Our DITA schemas cannot be fully read by the DITA Toolkit (parsing seems
to work, but transformation does not)
because the DITA Toolkit does not support TR 9401 catalogs, it does
appear to support XML Catalog.

I now view our options as: 1) modify the DITA Toolkit so it can resolve
our TR 9401 catalogs, or 2) create a transformation
engine that will migrate our DITA schemas on the fly from TR 9401
catalogs to "XML Catalog".

So, my focus has been on finding a way to modify the DITA Toolkit to
support TR 9401 catalogs.
It looks like the Norm Walsh java classes referenced below are just what
we need. I'm hoping
that I can incorporate his classes into the DITA ToolKit so that I can
call the transformation engine
with a parameter pointing to our schema within Arbortext Editor; example:
java TransformUsingXMLSchema ditaSample1.xml "C:/Program
Files/Arbortext/Editor/custom/doctypes/myTopic/myTopic.xsd" ditaSample1.htm

Of course, this is speculation on my part since I don't have the benefit
of seeing Mr. Walsh's classes, as yet.

We want to continue to use and develop DITA using the TR 9401 catalog
since that is the
only form Editor (5.3) supports. At the same time, we want to use an
open standard transformation engine
and the DITA Toolkit looks to be a viable choice, but for its lack of TR
9401 catalog support.