RE: [xml-dev] RE: Proposal: a building block approach to XML design

["Toby Considine" <Toby.Considine@gmail.com>]

Since we are  on an XML list, we are, I assume, talking informational
interfaces, which I think are closely allied to these idioms. I say closely
allied, because Service Interactions are meant to be agnostic of internal
mechanisms, and so are *not* the same as the fully developed idiom. A single
idiomatic interface should apply to several [similar] spaces, each based on
their internal idioms, and should allow for the development of new spaces
that have their own internal idioms. 

As long as we keep those distinctions straight, I think the functional
programming paragraph Roger quotes is spot on for this discussion.


"If something is not worth doing, it`s not worth doing well" - Peter Drucker

Toby Considine
TC9, Inc
TC Chair: oBIX & WS-Calendar
TC Editor: EMIX, EnergyInterop
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

  
Email: Toby.Considine@gmail.com
Phone: (919)619-2104
http://www.tcnine.com/
blog: www.NewDaedalus.com



-----Original Message-----
From: Costello, Roger L. [mailto:costello@mitre.org] 
Sent: Thursday, July 19, 2012 7:09 AM
To: xml-dev@lists.xml.org
Subject: [xml-dev] RE: Proposal: a building block approach to XML design

Hi Folks,

A while back I read this in a book on functional programming:

    The functional programmer, then, should approach a new 
    application by seeking to identify the programming idioms 
    common in that application area, and to define them as 
    (probably higher order) functions. Each particular application 
    program should then be built by so far as possible combining 
    these functions, rather than writing new code. (Perhaps for this 
    reason, such functions are often called combinators). The 
    benefits of such an approach are very rapid programming, 
    once the library of idioms is defined, and very often that 
    application programs are correct first time, since they are 
    built by assembling correct components.

It occurs to me that this applies to data design as well -- identify the
data idioms common in the application area.

Another name for "data idioms" is building blocks.

Thoughts?

/Roger

_______________________________________________________________________

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