The original Manifesto for Agile Software Development
http://agilemanifesto.org/ has a rather different flavor, IMHO.
"Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan"
These are principles, not technologies. It could be made more
relevant to XML by some much simpler tweaks:
"Individuals and interactions over processes and tools
Interoperating data over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a static schema"
It's not obvious to me how REST is more agile than SOA, RELAX is more
agile than XSD, etc. Certainly an agile XML developer would be ready
to use RELAX NG in a scenario for which it is more appropriate than
XSD *if* that improved customer collaboration, individual interaction,
etc. .... but that's almost certainly not *generally* true. Likewise
REST is often going to allow quick customer collaboration rather than
contract negotiation in a lot of straightforward cases where the
resources being transferred are human-readable information... but it
can simply delay the painful process of syntactic and semantic
alignment when those nice abstract resource representations hit real
world machine processed business documents and processes on each side.
These are all just tools. Getting ideological about tools is kindof
pointless. Would a Agile Home Improver say
"Agile pliers over rigid socket wrenches
Quick hammer and nails over tedious drills, screws, and screwdrivers
Universal adhesives over obsessive worry about which kinds of screws
or nails to use to join which kinds of materials"??? I don't think so
...
Maye I'm just surly because I recently spent twice as much time taking
an "agile" approach to a home improvement project as a Big Design Up
Front would have :-)
On 7/31/05, <> wrote:
> had fun using this bastardized version of Agile manifesto in a recent presentation to a large group of developers; I am not much of a methodologist...though there are threads running through Agile and XP dev methodologies that echo best practice IMHO;
>
> Agile XML(XREST) Manifesto
> -----------------------
> We are discovering ways of implementing
> and integrating software, Through this
> work we have come to value:
> XML processing over text processing (batch, make, etc...),
> REST over SOA (SOAP et al),
> RelaxNG over XML Schema,
> XPATH / XSLT over XQuery,
> That is, while there is value in the items on
> the right, we value the items on the left more.
>
> focusing on technologies as a 'solution' is of course a bit narrow minded, though in pure software development teams (which are devoid of doc heads) I am finding developers falling into these 2 distinct camps.
>
> Jim Fuller
>
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
>
