lisp/de.setf.xml — pull request #1 by spchamp (2014-12-28 19:30:13+00:00)
Title: Changeset for resolving issues encountered when evaluating CL-XML onto SBCL 1.2.6

Hello, Mr. Anderson.

I've been reviewing de.setf.xml, this week, for application in the MetaCommunity.info DataNet (MCi DNet) source trees. I've not had an opportunity to describe the proposed architecture for MCi DNet, but to make a short summary of the primary concept in that work area: It's a concept towards integrating OMG CORBA, OMG MOF, UML, SysML, and OMG ODM, within Common Lisp. I look forward to studying wilbur and de.setf.resource furthermore -- not to try to compete with Franz for Franz Allegrograph, but rather to endeavor to develop a completely free/open source framework for applying ontologies in Common Lisp, beside CORBA -- having made [a fork](de-setf/) of [CLORB](http://clorb.sourceforge.net/) -- and [McCLIM](http://common-lisp.net/project/mcclim/) -- also having made [a fork](https://github.com/MetaCommunity/mcclim/) of that system. Although I wish that I was presently able to provide any manner of a succinct UML diagrams for the proposed architecture, but I have been preferring to develop the architecture rather than to document it in its earliest component revisions.

Presently, I am evaluating de.setf.xml with an interest of loading the XML schema defined for [XMI](http://www.omg.org/spec/XMI/) version 2.4.2. XMI is a serialization format for [MOF](http://www.omg.org/spec/MOF/) meta-models and [UML](http://www.omg.org/spec/UML/), [SysML](http://www.omg.org/spec/SysML/), and [ODM](http://www.omg.org/spec/ODM/) models.
This review is made with SBCL 1.2.6, 64-bit architecture, on the Kubuntu Linux distribution. Although I've read of some concerns with regards to vendor-specific XMI serialization techniques, but perhaps those can be addressed fairly easily in Common Lisp.

In this short review, I've encountered a few issues when compiling and loading de.setf.xml in SBCL 1.2.6. Some of those issues, I was able to resolve, with the following changeset. Some of those issues, however, I am not immediately certain of how to resolve. I would welcome if you any able to offer any advice towards those issues' best resolution.

I've endeavored to document those issues inline to package.lisp, in this changeset -- making as 'SOLVED' the first issue that I was able to resolve, with this changeset. Certainly, once these issues would be resolved, then perhaps the comments I've added for describing the issues, in package.lisp, could be moved into separate documents, in some sort of a synax for an issue tracking system. Perosnally, I've been evaluating [YouTrack](https://www.jetbrains.com/youtrack/), for such regards

It appears that the changes I have made onto de.setf.xml may have resulted in some side-effects -- specifically, as with regards to the code generated by the ATN parser, onto the parser's grammar for XML -- and I am unable to immediately ascertain the origins of those changes, but I have included those changes in this changeset, for illustration.

My concern, presently, is in regards to an error occurring during evaluation of the following form:
> ` (xmlp:document-parser "")`

The evaluation of that form, after applying the following changeset -- in SBCL 1.2.6 -- is resulting in the following error message: "INCOMPLETE-PARSE signaled:" For purpose of illustration, I've included a partial backtrace of that error, in the comments presently contained in package.lisp

Certainly, I may be able to partially resolve the "Functions made reference to" issue, with a simple workaround as with regards to function aliasing, but I am not certain it that may present the most effective resolution to the issue. I presume that it may be an issue descendant from processing of the XML gammar.

Perhaps that also may be a simple issue to resole, then. I would like to share this present changeset, regardless, In the interest of illustrating this endeavor in applying CL-XML. I would welcome any advice that may serve to illustrate how the issues addressed in this changeset may be any more effectively resolved.

Good afternoon,

-- Sean Champ