[Home] [By Thread] [By Date] [Recent Entries]

  • From: Ihe Onwuka <ihe.onwuka@g...>
  • To: "Costello, Roger L." <costello@m...>
  • Date: Sat, 1 Oct 2016 14:05:26 -0400

But many people are  determined to do the work so  (conciously or otherwise) they unravel the declarativity and create a procedural framework which they feel comfortable working in.

Truth!

On Sat, Oct 1, 2016 at 1:18 PM, Costello, Roger L. <costello@m...> wrote:

Hi Folks,

The XML suite of technologies (XML, XSD, Schematron, XPath, XQuery, etc.) are declarative, not procedural, in nature; that is, the XML technology suite always favors declarative solutions over procedural ones, wherever such solutions are feasible. The reason is obvious: Declarative means the system does the work, procedural means the user does the work. That’s why the XML technology suite supports declarative structure definitions (XSD), declarative integrity constraints (Schematron), declarative queries (XPath and XQuery), and so on.

From the book SQL and Relational Theory by C.J. Date (p. 28):

The relational model is declarative, not procedural, in nature; that is, it always favors declarative solutions over procedural ones, wherever such solutions are feasible. The reason is obvious: Declarative means the system does the work, procedural means the user does the work. That’s why the relational model supports declarative queries, declarative updates, declarative view definitions, declarative integrity constraints, and so on.

Neat!

/Roger

 




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member