[
Lists Home |
Date Index |
Thread Index
]
- To: "Jeni Tennison" <jeni@jenitennison.com>
- Subject: RE: [xml-dev] Defining non-WXS datatypes
- From: "Dare Obasanjo" <dareo@microsoft.com>
- Date: Thu, 17 Jul 2003 16:25:30 -0700
- Cc: <xml-dev@lists.xml.org>
- Thread-index: AcNMn362RViprwEhR36djhMHS0YXeQAE4vzg
- Thread-topic: [xml-dev] Defining non-WXS datatypes
> -----Original Message-----
> From: Jeni Tennison [mailto:jeni@jenitennison.com]
> Sent: Thursday, July 17, 2003 1:10 PM
> To: Dare Obasanjo
> Cc: xml-dev@lists.xml.org
> Subject: Re: [xml-dev] Defining non-WXS datatypes
>
>
> I'm interested in which of the features you think are bad
> ideas?
Datatypes that require context to be correctly interpreted are a bad
idea. I can't see much benefit but lots of harm form actually
formalizing how to create more messes like QNames-in-content.
> What is it about type hierarchies that you're wary of?
They are unnecessary and can lead to difficulty in mapping them back to
existing domain models. On the other hand, what most folks really want
is just a way to specify type promotion or type equivalence rules. Most
programming and query languages don't need an integer to be the derived
type of a decimal number for one to perform operations involving both
types or to use them interchangeably.
--
PITHY WORDS OF WISDOM
If putting your nose into other people's business doesn't work; try
putting your heart into their problems.
This posting is provided "AS IS" with no warranties, and confers no
rights.
|