[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XML is text-only ... why?

• From: Len Bullard <len.bullard@u...>
• To: Philippe Poulard <philippe.poulard@s...>
• Date: Wed, 26 Sep 2007 11:14:34 -0500

Right.   Note that in this kind of application (RAD), XML is primarily a
means to push property values within the application context itself.  It is
the text representation of the property dialog passed to the application
builder.

The clarifying concept some years ago was that there is no clean divide
between document and data.  There is a continuum of applications which add
or ignore more information to the entity being transported.   The problem of
course, as Richard points out indirectly, is reversibility.  The questions
are 'to what form' and 'is this of value to a given point in that
continuum'?

In the RAD, it is illuminating to note where areas have to be declared
'safe', (won't be rewritten by the RAD) versus "unsafe to modify" (will get
stomped if the app is regenerated), which of these use XML and which don't.

len


From: Philippe Poulard [mailto:philippe.poulard@s...] 

Len Bullard a écrit :
> Here is another thought experiment:
> 
> Is this only XML?
> 
> <GEN:FieldValue Name="LastName" Type="TextBox" />
> 
> Is it useful as only XML?

For transporting it, yes

-- 
Cordialement,

               ///
              (. .)
  --------ooO--(_)--Ooo--------
|      Philippe Poulard       |
  -----------------------------
  http://reflex.gforge.inria.fr/
        Have the RefleX !
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.