OpenCyc Java API is declared obsolete, but OpenCyc release of Cyc KB is still fully supported

[AndrewSmart]

See: http://dev.cyc.com/cyc-api/faq.html
Need to decide what to do; fix issue #2 then what?
Could be useful if:

• Removed OpenCyc Java API.
• Added subrepos of relevant new Cyc Java APIs, from https://github.com/cycorp.
  • Perhaps make script to automate release matching.
    Would only be useful to help new developer quickly set up OpenCyc with new Java APIs. Hmmm, maybe not...

I think I should just focus on what I originally intended- to add features to enhance OpenCyc web interface's usability.

[nwinant]

You may be aware of much of this, but just in case it's helpful to your planning:

We haven't made a big announcement about the new Core APIs over on the SourceForge site yet, because we're still working on improving their compatibility with the OpenCyc KB. We hope to be able to announce something soon, but in the meantime, I guess we can't recommend moving away from the OpenCyc API (for the OpenCyc KB!) just yet.

Once the Core APIs are supported for the OpenCyc KB, they'll be available (and forkable, of course) via GitHub, while the artifacts will be built and distributed via Maven. For folks who don't prefer Maven, we'll also be providing a bundle (.zip & .tar.gz) for each release which includes (among other things) a single jar containing all of the Core API classes. That bundle will be downloadable via the CycCoreAPI's releases page on GitHub.