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

Re: A few lessons I have learned (June, '03)

• To: "Roger L. Costello" <costello@m...>
• Subject: Re: A few lessons I have learned (June, '03)
• From: "Chiusano Joseph" <chiusano_joseph@b...>
• Date: Fri, 06 Jun 2003 16:24:32 -0400
• Cc: xml-dev@l...
• Organization: BAH
• References: <3EE0E811.9136A671@m...>

<Quote>
- separate semantic definitions from application code
</Quote>

WSDL definitions (Operations, Messages, Parts, etc. are often dependent
on the systems that consume and process the messages whose format the
WSDL document describes - for example, "getLastTradePrice" may be the
name of an executable module on the receiver side (a Java Bean, C++
program, etc.). Does this violate the above principle? (in other words,
is the principle accurate?)

Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton

"Roger L. Costello" wrote:
> 
> Hi Folks,
> 
> Below are a few principles which I hold to be true:
> 
> 1. Frequently, data endures but the applications which processes the
> data comes and goes.
> 
> 2. Separate everything:
> 
>    - separate data from presentation
>    - separate data from applications that process the data
>    - separate semantic definitions from application code
>    - separate hyperlink definitions from data (put hyperlink
>      definitions in a linkbase)
> 
> 2. Freedom is not "do anything you want".  That is chaos.  Unbridled XML
> leads to chaos.  Freedom is brought about through discipline.  Bring
> order to instance data by conforming to a design pattern.
> 
>     The RDF Class/Property/Value design pattern seems like a
>     good choice to control the chaos.
> 
> 3. Minimize exacting requirements on the *form* of instance documents.
> Expect diversity of expression.
> 
>     Corollary: In designing schemas apply liberal quantities
>                of <any> and <all>; minimize use of <sequence>
>                and minOccurs="1".
> 
> 4. Take a step forward to machine understanding of instance data by
> documenting how the data relates to other things in the world: How does
> the class of data in the instance document relate to other classes of
> data? What are the characteristics of the properties?  Answers to these
> questions constitute a logical model.
> 
>     OWL seems like a good choice for declaratively expressing
>     logical models.
> 
> I invite your suggestions for deletions/extensions/modifications to this
> list. /Roger
> 
> -----------------------------------------------------------------
> 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://lists.xml.org/ob/adm.pl>

begin:vcard 
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@b...
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard

• References:
  • A few lessons I have learned (June, '03)
    • From: "Roger L. Costello" <costello@m...>

• Prev by Date: Re: Re: YAML Ain't Markup Language
• Next by Date: RE: Documents, data and markup: YAML Ain't Markup Language
• Previous by thread: Re: A few lessons I have learned (June, '03)
• Next by thread: Re: A few lessons I have learned (June, '03)
• Index(es):
  • Date
  • Thread