OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] W3C Schema: Resistance is Futile, says Don Box

[ Lists Home | Date Index | Thread Index ]
  • To: "'Matt Gushee'" <mgushee@havenrock.com>,<xml-dev@lists.xml.org>
  • Subject: RE: [xml-dev] W3C Schema: Resistance is Futile, says Don Box
  • From: "bryan" <bry@itnisk.com>
  • Date: Tue, 11 Jun 2002 17:16:47 +0200
  • Importance: Normal
  • In-reply-to: <20020611144817.GV650@swordfish.havenrock.com>

On Tue, Jun 11, 2002 at 04:22:55PM +0200, bryan wrote:
> Data entry is a user interface issue. There are plenty of applications
> out there that allow you to type in "June 11, 2002", then store it as,
> e.g., 2002-06-11. I don't think anyone is saying end users should be
> subject to such rigid constraints, or if they are they should be
> silly.
> And if the user interface is an xml editor for writing up your
> or what have you? The person entering the info for the catalog is
> to my mind, a user.
Matt wrote:
[Well, that's a valid concern. But to me it still seems like more of an
application issue than an XML issue. I think it's important to define
what kind of user we are talking about (which I suspect many vendors of 
XML editors haven't done). If it's someone like me, well, I'm a
developer (as well as a writer), and I don't even use an XML editor most
of the time: I do most of my work in vi, and am accustomed to rigid
language requirements. So for people like me it is no burden to look up
and consistently use the correct date format.]

That's true but there are intermediate users as well, and even so if
your natural inclincation is to write 01-23-1977...ah well, but here I'm
getting off track since there is another concern that if XSDL validation
is so patchy that one has to write all sorts of other code to validate
and transform dates into a dateformat that XSDL understands I think
again the utility of XSDL comes into serious question. 

[If on the other hand, you're talking about clerks, professors, or
physicians, it seems to me that having those people (with the possible
exception of professors) work with raw XML is asking for all kinds of
trouble in any case. I don't see a good reason why people who can't
think in code and have no particular interest in it should have to see
it. They should have friendly GUIs to work with. If those aren't
provided, well, to my mind the problem lies with their management or
with the software vendor.]

I think people can be taught to think in Xml rather easier than they can
be taught to think in "code", code being a far wider field of discipline
than xml is. Lots of people were taught to think in html, and look how
well that turned out. :)

[By the way, did you mean for this to be off-list?]
no I just posted in two separate posts


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS