#2713 Enforce loose validation of CIM-XML documents

closed-fixed
Dave Blaschke
jsr48-client
5
2013-12-13
2013-11-20
Dave Blaschke
No

CIM-XML requires to apply loose validation, as stated in DSP0200:

In this discussion, any reference to well-formed or valid XML documents has the standard meaning defined in Extensible Markup Language (XML).

XML document type definitions (DTDs) are restricted to be either well-formed or valid. However, this document also uses the term loosely valid to apply to XML that removes any attributes or elements in the XML document that do not appear in the CIM XML DTD. The resulting document is valid with respect to the CIM XML DTD and is therefore loosely valid.

In effect, a loosely valid document is valid with respect to the CIM XML DTD apart from having additional attributes or elements not defined by that DTD. The concept is very similar to that of an open content model as defined by the working draft on XML Schemas, expressed within the more limited scope of DTDs. One corollary of this definition is that any XML document that is valid with respect to the CIM XML DTD is also loosely valid.

1 Attachments

Related

Bugs: #2714

Discussion

  • Dave Blaschke
    Dave Blaschke
    2013-11-22

    This mainly affected the DOM parser, which used a searchFirstNode method to retrieve the first child it was looking for, process it an return without regard to other illegal children.

    The SAX parser did have to be modified to ignore unknown children instead of throwing a parse exception.

     
  • Dave Blaschke
    Dave Blaschke
    2013-11-22

    • status: open --> open-fixed
     
  • Dave Blaschke
    Dave Blaschke
    2013-11-22

    Patch sent for community review. During a 2 week period any exploiter may comment on the patch, request changes or turn it down completely (with good reason). For the time being the patch is part of the "Experimental" branch in CVS.

     
  • Dave Blaschke
    Dave Blaschke
    2013-12-09

    • status: open-fixed --> pending-fixed
     
  • Dave Blaschke
    Dave Blaschke
    2013-12-09

    The community review is completed and we received no substantial criticism. Therefore the patch has been approved and merged into the "HEAD" branch. The next release will pick it up.

     
  • Dave Blaschke
    Dave Blaschke
    2013-12-13

    • status: pending-fixed --> closed-fixed
     
  • Dave Blaschke
    Dave Blaschke
    2013-12-13

    The patch was picked up by release 2.2.5 and will be closed.