I disagree. XSD is not an OO programming language and defines types and structures in its own, very peculiar, way.
I was not saying XSD is an OO programming language at all. Merely that that XSD's describe types and structures and that code uses types and structures.
The act of "converting schema defined types into AS VO classes" will require defining and applying several conversion rules.You can either avoid documenting those rules/choices (raising the level of chaos in the world) or store them somewhere.Storing them in an XSD is probably convenient since it is a formalism already being used in this bespoken project.
Yes one could write a an xml schema to validate schemas that a convertor would convert. This would be useful if the tool had constraints on the input schema. I'm not soo sure though that constraints would be needed as I do not think it would be too complex to parse and then generate VO's from a schema.
I am thinking one could build an internal tree of the schema structure (as most XML editors do - and then represent this to the user in a variety of ways!) and hence use/walk that tree to generate the classes. Hence take any valid xml schema and convert to VO classes.
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
