Hi Folks, There is an Apache technology called NiFi. It is used to distribute data. [1]
A feature of NiFi is that a NiFi application will automatically generate metadata about the data it
ingests. The metadata is formatted as XML, which has this form: <properties> Each item of metadata is represented with an <entry> element. The “key” attribute contains the name
of the metadata item, and the value of the <entry> element contains the value of the metadata item. What are the advantages and disadvantages of this type of XML design? Advantages:
Disadvantages: There is likely to be a constraint (relation) between an <entry>’s @key value and the <entry>’s content: Examples of co-constraints:
XML Schema 1.0 doesn’t support co-constraints. [2] So, you need to supplement XSD with Schematron.
In some environments, it is simply not feasible to perform both XML Schema validation and Schematron validation.
Consequently, co-constraints go unexpressed. The design hampers the ability to use XML Schema’s powerful
constraint mechanisms. Thus, the design hampers the ability to perform powerful error-checking.
Do you agree with these advantages and disadvantages? Are there other advantages and disadvantages? /Roger [1] https://nifi.apache.org/ [2] Yes, I know that XSD 1.1 supports co-constraints, but (I assert, without evidence that) there
is lesser support for XSD 1.1 than for XSD 1.0 or for Schematron. |