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

loose coupling, was Re: Early Draft Review: XQuery forJava (JS

• To: Michael Kay <michael.h.kay@n...>
• Subject: loose coupling, was Re: Early Draft Review: XQuery forJava (JSR 225)
• From: Burak Emir <Burak.Emir@e...>
• Date: Wed, 30 Jun 2004 09:47:38 +0200
• Cc: xml-dev@l...
• In-reply-to: <20040629081952.HGFO2927.mta05-svc.ntlworld.com@Turtle>
• References: <20040629081952.HGFO2927.mta05-svc.ntlworld.com@Turtle>
• User-agent: Mozilla Thunderbird 0.5 (X11/20040208)

Michael Kay wrote:

>>The issue is relevant to ad hoc queries but it's moot for 
>>repetitive queries,
>>such as for generating a monthly publication. 
>>    
>>
>
>That statement confuses me, and not only because Americans appear to use the
>word "moot" in the opposite of its original English sense of "arguable".
>  
>
I wonder whether to which extent the interpretation of words like moot 
influences the quality of API designs. I always though argueing (with 
the goal of agreement) was a good thing, but by now I come to think that 
I might be too idealist.

>The benefit of a string interface is that it gives looser coupling between
>systems. The benefit of a custom syntax/protocol is that it gives earlier
>validation. The experience of the last few years is that loose coupling
>tends to win, across most application scenarios. Hence XML.
>
>  
>
I am not sure of the "loose coupling" argument in the context of 
large-scale software development.

You put element names, variables names in your query strings. You might 
rely on the schema of the data to process the query result.

Now the schema evolves, you have to change your queries - is it easier 
to change (=>loosely coupled) if you have your queries in objects, or if 
you have them in strings ?

cheers,
Burak

• References:
  • RE: Early Draft Review: XQuery for Java (JSR 225)
    • From: "Michael Kay" <michael.h.kay@n...>

• Prev by Date: Re: Early Draft Review: XQuery for Java (JSR 225)
• Next by Date: Re: Early Draft Review: XQuery for Java (JSR 225)
• Previous by thread: Re: Early Draft Review: XQuery for Java (JSR 225)
• Next by thread: Re: Early Draft Review: XQuery for Java (JSR 225)
• Index(es):
  • Date
  • Thread