Hi everyone.

The last of the five problem statements for XML parsing rework is:
    AI manifests have validation holes.

The issue is that in the Sysmap Manifest (formerly Criteria Manifest), 
values attached to criteria (e.g. the min and max value of a range of IP 
addresses) are not bound to the criteria tightly enough by the schema 
for their validation to be thorough.

So, there is a simple "functional requirement" that the Sysmap Manifest 
validate better by more tightly coupling criteria value types to the 
criteria themselves in the schema.

Since this is a simple problem, saying anything more than this becomes 
implementation.  When I look at the strawman now, I see implementation 
details there, not a high-level description of what needs to be done.

As such, I don't see a need for a functional specification for this.

Anyone have feedback on this?  If yes, please let me know by COB 5/28.

- - -

I would like to document here my proposed solution, for the record.  
This comes from the strawman.

Some criteria take only a value, some take a range of values.  I suggest 
making better use of the schema and providing a clearer syntax by 
replacing the format of a criterion and putting the "min", "max" or 
"value" values explicitly as in the following:

        <criteria_set>
                <IPv4 min=1.2.3.4 max=5.6.7.8>
                <MAC value=2.3.4.5>
                <MEM min=1Gb>    <!-- unbounded max -->
        </criteria_set>

-Why change from current implementation?

        - More compact syntax.
        - More robust checking vs schema.
        - No need for "unbounded";  just leave off min or max
          attribute.

    Thanks,
    Jack

Reply via email to