[Bug 4978] Is smlerr:output necessary?


------- Comment #5 from pratul.dublish@microsoft.com  2007-11-12 20:37 -------
The primary scenario for this was impoverished devices that were incapable of
doing SML model validation but wanted to perform some actions based on
validation errors. An example is a management controller card that enforces a
desired configuration on a computer. The desired config can be captured as an
SML model, the controller card can discover the current state of the machine
and send it to a remote server for validation against the SML model, get the
structure error output, and use it to peform corrective actions to bring the
computer's state in compliance with the desired config. It was felt that
defining a mechanism, albeit optional,  in the SML spec will encourage vendors
to adopt and imoplement it. 

Note that the above scenario is partially addressed by smlerr:output since it
assumes that all desired configuration will be captured through Schematron
rules. If SML identity constraints and target* constraints are used, then there
is no standard mechanism for reporting these errors. 

Received on Monday, 12 November 2007 20:37:21 UTC