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

Re: XQuery types was Re: Yet another plea for XUpda


Re:  XQuery types was Re:  Yet another plea for  XUpda
Uche Ogbuji wrote:

> I think this is all an unfortunate misunderstanding.
>
> Jonathan, Dare and I were talking about static types (I also use the term
"imperative types") in our discussion before XQuery formal semantics were
brought up.  I dropped out of the discussion at that point because I have
not read this document, but I think it's reasonable to assume that Dare was
continuing to talk about static types when he said "types".  This is a very
common abbreviation among programmers (though I wish it weren't), and you
yourself later on admitted you probably understood Dare as such.  It's also
useful to remember that the use of the word "class" in object oriented
development is very different from its more general use.
>

Yes I see, however when "type" or "class" is used in the context of a
"formal semantics" there is no notion of "compile time type checking" vs.
"run time checking" (a.k.a. schema validation).

In any case let's not continue the misunderstanding -- though clearing this
up _is_ useful.

>
> Anyway, back to the main point.  I agree with your broader definition of
types as being defined by constraints, and this is *precisely* why I am
always ridiculing the W3C efforts which put so much effort into static
typing at the behest of their SQL and procedural programming backgrounds (I
guess).  Programmers don't need to become pure mathematicians to appreciate
this: Bertrand Meyer provides much of the essence in his own writing about
object-oriented development.
>
> Also, I explore a bit of this in one of my Thinking XML column
installments.  I purposefully use lay/programmer language in it because the
column is specifically billed as being for programmers, not philosophers.
>
> http://www-106.ibm.com/developerworks/xml/library/x-think8.html
>

Well written.

As an aside, I have come to the understanding that way RDF allows the
"rdf:type" property to be derived via subPropertyOf e.g. your
"vcard:contactType" causes hairy problems for lots of classification
software (and we realize that there actually is software out in production
which can do real things with classifications, e.g. CLASSIC, FaCT etc.)

Jonathan


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.