There was no mention of XML Schema there,
although Howard mentioned the term "schema"
(lowercase).
So, XmL
is not XML and sChema is not Schema to you!
Matters not.
The concept/term
'schema' existed far before XML Schema was
introduced and its original meaning is still the most widely
known.
I figured out that he
wanted to serialize XML into AS automatically.
That is what XLEFF does in
the case of the Component Architecture classes (and more
generically via the XModel class).
No he doesnt want to serialize XML
into AS. He wants to convert XML schema types into AS types (specificaly VO
classes). This is quite a different ball game.
XLEFF is converting
strictly typed/validated XML into strictly defined AS classes.
see my next reply about VO
classes.
I see now that his original
intention was literal (generate AS classes from XML Schema
sources).
It is very ambitious,
especially because there is no similarity/correspondence between AS and
XSD.
Of course there are
similarities. An XSD defines types and structures, as does any OO programming
language.
I
disagree. XSD is not an OO programming language and defines types and
structures in its own, very peculiar, way. Following your logic, it will
cost you less to find similarities between English and Chinese since they are
both used to communicate, as does any human language.
Maybe, it could be helpful to start such
project by producing an XSD of ActionScript. Such definition would act as a
sort of "Meta-Schema", providing the necessary requirements of the
intended "XSD to AS Class generator".
Why on earth would that be helpful? We are talking about converting
schema defined types into AS VO classes.
The
weight of being clear should be on the shoulders of whoever asks first. I
wonder how many, among the readers of this post, are familiar with
VO (Value Object?) classes. The concept comes from Java world and,
personally, I am still wondering if it is of any practical use within the AS
domain.
However, coming to your question:
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.
Hi
there,
Please note that I replied
to the very first message, trying to help.
There was no mention of XML
Schema there, although Howard mentioned the term "schema"
(lowercase).
I figured out that he
wanted to serialize XML into AS automatically.
That is what XLEFF does in
the case of the Component Architecture classes (and more
generically via the XModel class).
I see now that his original
intention was literal (generate AS classes from XML Schema
sources).
It is very ambitious,
especially because there is no similarity/correspondence between AS and
XSD.
Maybe, it could be helpful
to start such project by producing an XSD of ActionScript. Such definition
would act as a sort of "Meta-Schema", providing the necessary
requirements of the intended "XSD to AS Class
generator".
-----Original Message-----
From:
jtgxbass [mailto:[EMAIL PROTECTED]]
Sent: 22 September 2006
13:22
To: Open Source Flash Mailing List; David
Holroyd
Subject: Re: [osflash] XMLSchema ->
ActionScript
Antonio:
You
may try XLEFF ( www.xleff.org), which is
based on a mechanism very
similar to the one you are looking
for.
?? That has nothing to do with what David
is after.
Though it does look neat ;)
David:
The
thing that makes it a complex problem is that XMLSchema is
rather
complex. So, I'll just ignore anything that looks tricky
for the
moment.
Yes an XML schema can become quite complex. But if they are being
authored for use by you, perhaps you could require certain
constraints?
_______________________________________________
osflash
mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
