Is the physical .xsd used in the runtime process you're describing? It didn't look like it was.
It looks like the xslt is peppered with different parts of the original person.xsd.
Your xslt is tied to this particular schema (Person.xsd). I'm looking for a solution that works for any schema.
The process might look like this:
1) Create a schema by hand.
2) run a code generator that creates a functional UI solely based on the information found in the schema. Like your solution, the UI would contain
the four CRUD methods to maintain instance documents of the schema.
3) The generated UI could be later enhanced with meta data that suggested which UI controls to use (radio buttons, check boxes, lists, etc).
Chiba, Cocoon Forms and SchemoX come close to these requirements. HOwever, they're either not very mature or forgotten/unattended projects.
SchemaWizard (http://ptlportal.communitygrids.iu.edu/schemawizard/index.html) is a good start, but it also looks like a 'lost child'.
Perhaps we need to pool our resources to get this done.
Erik Ostermueller
erik.ostermueller@fnf.com
|
Previous Message
