![]() |
![]() | ![]() | ![]() | Altova Mailing List Archives>Archive Index >xml-dev Archive Home >Recent entries >Thread Prev - RE: [xml-dev] What is coupling? [Was: 3 XML Design Principles] [Thread Next] Re: [xml-dev] What is coupling? [Was: 3 XML Design Principles]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> > | ![]() | ![]() | ![]() |
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | |||
|
