Lists Home |
Date Index |
Some years ago during the IADS work, our chief designer said that
any language (at that time, SGML) that enabled mixed content
should be eliminated from the universe. Instead, the follow
on, XML, thrived and won. While I understand the parser-centric
data model position, history is not on the side of eliminating
It's not a design issue; it is a scope of control issue.
The mixed data model is very common and impossible to
eliminate unless the designer owns all ends of the pipes.
This isn't likely given a web distribution. Even
in intranets, we see this a lot. It comes down to
where in the pipeline the detection of mixed data models
The problem of schema profiles will be that the profiles
have to be named. A lot of process rot ensues.
From: Ed Day [mailto:firstname.lastname@example.org]
I suppose this is case of "document-centric" vs "data-centric" application
thinking (I am in the latter camp). It would seem this might be a good
place to start when breaking down schema profiles.