DOMConfiguration

• Maintains a table of boolean, String, and Object parameters such as canonical-form and error-handler

• Makes it possible to change what normalizeDocument() does by modifying these parameters

• Java binding:

  package org.w3c.dom;
  
  public interface DOMConfiguration {
  
    public void    setParameter(String name, Object value) throws DOMException;
    public Object  getParameter(String name) throws DOMException;
    public boolean canSetParameter(String name, Object value);
    public DOMStringList getParameterNames();
  
  }

• Standard parameters include:

  canonical-form, default false, optional

  Canonicalize the document according to the rules of Canonical XML within the limits of DOM

  cdata-sections, default true, required

  Keep CDATASection nodes in the document

  check-character-normalization, default false, optional

  Check if the characters in the document are Unicode normalized in normalization form C

  comments, default true

  Retain Comment nodes in the document.

  datatype-normalization, default false, optional

  Use schema-normalized values

  element-content-whitespace, default true, optional

  Retain white space in element content (a.k.a ignorable white space)

  entities, default true, required

  Include EntityReference nodes in the document

  error-handler, required (non-boolean)

  A DOMErrorHandler object

  infoset, default true, required

  Set various parameters to keep all the information defined in the XML InfoSet

  namespaces, default true, optional

  Use namespace rules

  namespace-declarations, default true, required

  Include namespace declaration attributes as Attr nodes in the document.

  normalize-characters, default false, optional

  Normalize characters according to Unicode NFC

  schema-location, optional

  a list of schema URIs, separated by whitespace

  schema-type, String, optional

  an absolute URI such as http://www.w3.org/2001/XMLSchema or http://www.w3.org/TR/REC-xml (DTD) representing the type of the schema language

  split-cdata-sections, default true, required

  What to do when a CDATA object contains a ]]>

  validate, default false, optional

  Validate against the schema when normalizing

  validate-if-schema

  Validate against the schema when normalizing if one is found; otherwise don't bother

  well-formed, default true, optional

  fully check nodes for well-formedness

• Implementations may also define their own custom parameters