Cart
[Home] [By Thread] [By Date] [Recent Entries]
>> Hallelujah something we can agree on. The business application should always be the >> repository of business rules and validation is one aspect of that. I only consider XSD >> useful as an optimisation so that you don't consume cycles only to find something that >> you could have discovered at the front door. This is especially true for cases where the >> business application isn't 24/7 but you want to ensure customers can still trade at any >> time and have a reasonable prospect of a successful transaction. Typically I don't use >> XSD for the purpose of validation all that much (although I might be more persuaded by >> v1.1), since it's often much too blunt a tool for that and too difficult to organise for >> anything more than simple grammar checking. I do find utility for it elsewhere though. CAM (Content Assembly Mechanism) was developed, IIANM, as a publishable way to make the ontological/business validity assertions over and above the semantic matching defined by XSD. tc -----Original Message----- From: Fraser Goffin [mailto:goffinf@g...] Sent: Tuesday, April 09, 2013 3:07 PM To: Simon St.Laurent Cc: xml-dev@l... Subject: Re: Fwd: Not using mixed content? Then don't use XML > No. I would propose moving the other direction, treating all of the > rules as "business" and not relying on schema for any layer of that.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
