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

Re: Build applications using the "simplicity stack"

• From: Amelia A Lewis <amyzing@talsever.com>
• To: xml-dev@lists.xml.org
• Date: Mon, 31 Mar 2014 21:46:32 -0400

Hmmmm.

On Tue, 1 Apr 2014 12:35:36 +1100, Stephen Cameron wrote:
> Related to the current 'Data is primary .... why?' thread, once you have
> your carefully crafted data-model what can you with it?
> 
> Thinking in terms of a simplicity stack of non-mutually-exclusive options
> (cost-effectiveness is a better notion, simple might not be cost-effective
> in the long term, one option should build on another if possible).
> 
> The combination of a data-model in XML Format (schema) and XML technologies
> is a powerful combination at the bottom of the stack, here are some
> expressions:

0) All the things that we haven't invented yet, that work with this 
documented format or that work with a documented format to which this 
one can be losslessly translated.

> 1) Schema Generated Forms (XML Editors)
> 2) Configuration for a data-driven/data-event programming paradigm.
> 3) Schema-aware "dynamic" language procedural programming before fully
> object-oriented.
> 4) Smarter generic data-browsers (query interfaces) via schemas as resource
> 'meta-representations'.
> 5) Smart (user-friendly) databases based on a conceptual/semantic
> data-models.

Amy!
-- 
Amelia A. Lewis                    amyzing {at} talsever.com
It's is not, it isn't ain't, and it's it's, not its, if you mean it is.
If you don't, it's its.  Then too, it's hers.  It isn't her's. It isn't
our's either.  It's ours, and likewise yours and theirs.
                --OUP Edpress News

• Follow-Ups:
  • Re: Build applications using the "simplicity stack"
    • From: Stephen Cameron <steve.cameron.62@gmail.com>

• References:
  • Re: Build applications using the "simplicity stack"
    • From: Arjun Ray <arjun.ray@verizon.net>
  • Re: Build applications using the "simplicity stack"
    • From: Stephen Cameron <steve.cameron.62@gmail.com>