Lists Home |
Date Index |
When beavering, beware the introduction of gators to
reduce the rate of dam builders. From that day forward,
fishermen need rifles.
Actually, the InfoSet introduction was one of the
features of XML system specifications that distinguished
it from SGML. While we used to have the ESIS arguments,
the infoset was for me, when explained, a clarifying
moment because it enabled me to union different systems
under a unifying set of concepts.
But I don't think they need to be rejoined as much
as we need to always be aware when the introduction
of a new requirement puts gators in the wildlife
refuge, and then only because we have to tell the
fishermen to buy extra gear. Syntax is like water.
The Infoset is a dam.
From: John Cowan [mailto:firstname.lastname@example.org]
"Bullard, Claude L (Len)" scripsit:
> Because it makes a difference in what is normatively
> referenced if one knows which set of requirements
> contain system specifications that introduce system
> dependencies. It is not a matter of inferior or
> superior, but of lifecycle design.
Fair enough. But IMO the Infoset and the Syntax were separated at
birth, and must sooner or later be rejoined. Until that day, we
humans beaver away at keeping them consistent.