[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
RE: [xml-dev] What's your ideology for how applications should be created?
- From: "Len" <cbullard@hiwaay.net>
- To: "'Costello, Roger L.'" <costello@mitre.org>, <xml-dev@lists.xml.org>
- Date: Sat, 20 Dec 2008 12:00:36 -0600
And that rolls us back to the techniques of 1986 when we were designing
documents to mimic first MIL-D-38784 then the US Navy Work Packages, or the
legal documents of GML.
It's SGML retro-fashion.
The first crack in the ice is when someone suggests that the documents being
passed reflect not a workflow but an aggregate of workflows packaged for
passing to a workflow that is not document or information production, but
the application of the information produced, in those cases, to the
technical maintenance of systems. Then someone notices the superior
addressability of UNIX manpages and/or framing techniques in AI and we once
again go through the loop.
At what point do we escape that loop at a higher dimension of functional
application and efficient production?
len
-----Original Message-----
From: Costello, Roger L. [mailto:costello@mitre.org]
Sent: Saturday, December 20, 2008 7:12 AM
To: 'xml-dev@lists.xml.org'
Subject: [xml-dev] What's your ideology for how applications should be
created?
Hi Folks,
"An ideology is ... a conceptual framework with the way people deal with
reality." [Alan Greenspan]
What's your ideology for how applications should be created?
I oftentimes see parts and pieces of a conceptual framework for application
design, but rarely do I see a complete framework.
What appeals to me about Michael Kay's article[1] is that it is a complete
conceptual framework (ideology), expressed by an extraordinarily bright
individual, possessing a wealth of experience. (much like Alan Greenspan)
Here is the Michael Kay ideology, in a nutshell:
Create workflow-based applications. Design XML documents to mimic documents
in the physical world. Store the XML documents centrally, in an XML
database. Pass around URLs to the documents. Use an all-XML solution; avoid
using imperative languages.
What's your ideology for how applications should be created?
/Roger
P.S. Michael Kay, I hope that I have accurately portrayed your ideology.
Please correct any errors.
[1] http://www.stylusstudio.com/whitepapers/xml_workflow.pdf
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]