Hi Folks,
Lately, to my surprise, I have been hearing more and more people advocate the use of application code to enforce data constraints (data rules). Particularly the complex data rules you might expect to find in Schematron. Their argument, presumably, is that for most domain experts and business people, data rules such as the following are gibberish:
<sch:pattern id="Knowledge-about-radio-
stations" >
<sch:rule context="GeographicArea">
<sch:let name="stations" value="RadioStation"/>
<sch:assert test="
every $s1 in $stations, $s2 in $stations satisfies
if (pred:Disjoint($s1, $s2)) then
number($s1/band) ne number($s2/band)
else true()
">
Radio stations broadcast on different frequency bands (within an area).
</sch:assert>
</sch:rule>
</sch:pattern>
Since they are gibberish, you might as well have the developers implement the rules in application code. Out of sight, out of mind.
I guess that’s their argument.
I thought the world had moved beyond such thinking, years ago. I thought that everyone had come to the agreement that burying data rules in application code is a bad idea.
So what happened?
Did the world suddenly get amnesia? Did the experience from the last 20 years reveal that expressing data rules in text, declaratively didn’t work out as desired?
/Roger