Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] What is coupling? [Was: 3 XML Design Principles]

From: Robert Koberg <rob@------.--->
To: "Bullard, Claude L (Len)" <len.bullard@----------.--->
Date: 2/1/2005 7:00:00 PM
Bullard, Claude L (Len) wrote:
> Cohesion and coupling:
...
> and of course, the ultimate expression of homophilic principles, the Law of
> Demeter: 
> "Only talk to your friends."  For programmers, there are lots of articles on
> this one.
> 
> http://www.cmcrossroads.com/bradapp/docs/demeter-intro.html

I am having trouble applying OO to XML, but I read this from the above 
article:

"The Law of Demeter says that if I need to request a service of an 
objects sub-part, I should instead make the request of the object itself 
and let it propagate this request to all relevant sub-parts, thus the 
object is responsible for knowing its internal make-up instead of the 
method that uses it."

To me, if I have a nested structure in an XML instance and using XSL on 
that I apply-templates (flow through the instance doc) and only do what 
is in the XML. If I come across something that is a reference to 
something else I can go out, get it, apply-templates on it and continue 
where I left off.

If I have a flat structure in an instance doc I have to assume where 
things go and place them in a more rigid way.

Am I just not getting it?

-Rob

> 
> len
> 
> 
> 
> 
> 
> -----------------------------------------------------------------
> 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>
>


transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent