Create an FML DTD or XSD

Should be with modello

Added modello stuff in r568106

We need to publish fml-1.0.0.xsd at http://maven.apache.org/xsd/, as it's referenced in the mdo file.

I am afraid our current modello-generated xsd is unusable, I couldn't validate any fml with it. One problem is the default namespace that is generated (that's maybe fixed in modello-1.0-alpha-15 with MODELLO-46), the other is that all attributes are written out as elements in the xsd (see MODELLO-49). We can't publish it like that, so I propose to move this issue to a later release.

Pushing it to a later release is fine by me.

I just fixed MODELLO-49
With the patch provided, 3 problems are away:

• XML attributes
• flat list
• namespace

There is still one problem to validate existing test.fml: answers contain HTML code not enclosed with <![CDATA[...]]>, which is not supported by the simple xs:string type generated.
I have to find a way to support that.
Any thoughts?

Herve,

You can use the XML Schema any tag to define a wildcard

See: http://www.xml.com/pub/a/2002/11/20/schemas.html?page=4#wildcards

Given that most people won't be using namespaces with their XML, then you should allow any namespace in the any tag.

e.g.

<xs:element name="answer">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="blah" type="xs:string"/>
      <xs:any minOccurs="0" processContents="skip" namespace="##other" />
    </xs:sequence>
  </xs:complexType>
</xs:element>

Thanks David

Maven 1 faq.xsd contains:

<xsd:complexType mixed="true">
    <xsd:sequence>
        <xsd:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded" /> 
    </xsd:sequence>
    <xsd:anyAttribute namespace="##other" processContents="lax" /> 
</xsd:complexType>

How does it compare to your proposal?

Then the other question is: how to represent it in fml.mdo?
Actually, answer is coded as:

<field>
  <name>answer</name>
  <type>String</type>
  ...
</field>

Should it be transformed to:

<field>
  <name>answer</name>
  <type>XML</type>
  ...
</field>

or

<field xml.stringAsXml="true">
  <name>answer</name>
  <type>String</type>
  ...
</field>

or ... ?

The maven1 faq.xsd looks good, go with that, since I just made mine up as an example, where-as I imagine the maven1 faq.xsd has been tested.

I don't know about modelo, so no comment.

I added xsd files in r703144

As for a review of the XSD: One could try to create unit tests that
a) use a couple of interesting example documents as input which we know are valid
b) push these documents through an XML parser in validating mode which employs the XSD
If the sample documents pass the validation, we have some assurance that the XSD captures the intended structure.

working on Modello, I found the feature we needed to handle HTML code not enclosed with {{<![CDATA[...]]>}}: it's <type>DOM</type>