Subject: XHTMLT Modularization 1.1 - Second Edition Example

All:

Subject: XHTMLT Modularization 1.1 - Second Edition Example

 

I believe that that the modular XHTML approach to the creation of web
documents is very important. It could be the basis of creating truly
portable applications including an office suite for html 5.  Unfortunately,
I cannot get the first example to validate.

 

I have tried to validate the schemas listed in XHTMLT Modularization 1.1 -
Second Edition, 

W3C Proposed Edited Recommendation 14 April 2010, B.4.1. Creating a simple
Document Type. I started with
http://www.w3.org/MarkUp/SCHEMA/examples/simpleml-module-1.xsd. I downloaded
the schemas from the ZIP archive. Since validation errors appeared in both
XMLSpy and oXygen, I tried to trace back the source of the errors.
Unfortunately, this is quite difficult because of the use of unqualified
declarations, absence of prefixes.  

When I attempted to validate simpleml-1_0, the error message from oXygen for
was:

 

SystemID: http://www.w3.org/MarkUp/SCHEMA/xhtml-basic10-modules-1.xsd

Engine name: Xerces

Severity: error

Description: derivation-ok-restriction.2.1.2: Error for type
'xhtml.version.attrib'.  The attribute use 'version' in this type has type
'FPI', which is not validly derived from 'CDATA', the type of the matching
attribute use in the base type.

Start location: 121:42

End location: 121:53

URL: http://www.w3.org/TR/xmlschema-1/#derivation-ok-restriction

 

SystemID: http://www.w3.org/MarkUp/SCHEMA/xhtml-basic10-modules-1.xsd

Engine name: Xerces

Severity: error

Description: src-redefine.7.2.2: AttributeGroup 'xhtml.version.attrib' does
not properly restrict the attributeGroup it redefines; constraint violated:
'derivation-ok-restriction.2.1.2'.

Start location: 121:9

End location: 121:21

URL: http://www.w3.org/TR/xmlschema-1/#src-redefine

 

The error message from XMLSpy for 

simpleml1 stated that xhtml-basic10-modules-1.xsd was not valid. I believe a
simple make file might help. The location of xhtml.version.attrib is not
obvious.

The schema doesn't appear to be valid by itself (as a part of another
schema, it might still be OK).

                File
http://www.w3.org/MarkUp/SCHEMA/xhtml-basic10-modules-1.xsd is not valid.

                                Redefining attribute group definition
'xhtml.version.attrib' must be a valid restriction of its redefined
counterpart 'xhtml.version.attrib'.

                                                Error location: xs:schema /
xs:redefine / xs:attributeGroup

                                                Details

 
derivation-ok-restriction.2.1.2: The type definition 'FPI' of attribute
declaration 'version' is not validly derived from type definition 'CDATA'.

 
src-redefine.7.2.2: Redefining attribute group definition
'xhtml.version.attrib' must be a valid restriction of its redefined
counterpart 'xhtml.version.attrib'.

 

redefine

A comment in Section 4.2.4 of W3C XML Schema Definition Language (XSD) 1.1
Part 1: Structures, W3C Working Draft 3 December 2009brings into question
the use of the redefine element.

Section 4.2.4 Including modified component definitions (<redefine>)

Note: The redefinition feature described in the remainder of this section is
.deprecated. and may be removed from future versions of this specification.

Schema authors are encouraged to avoid its use in cases where
interoperability or compatibility with later versions of this specification
are important.

Editorial Note: Priority Feedback Request

The Working Group requests feedback from readers, schema authors,
implementers, and other users of this specification as to the desirability
of retaining, removing, deprecating, or not deprecating the use of
<redefine>. Since the <override> facility provides similar functionality but
does not require a restriction or extension relation between the new and the
old definitions of redefined components, the Working Group is particularly
interested in learning whether users of this specification find that
requirement useful or not.

 

My long-term interest is to use XHTML 5 that includes forms with one of my
CytometryML schemas
(http://www.newportinstruments.com/cytometryml/cytometryml.htm) to create
strongly typed forms. The use of CSS for formatting will be simplified by
having the HTML and CytometryML schemas independent of each other. This
would permit the elements of a complexType to be used in a sentence
contained in a <p> element, which could include a class attribute.  Could
something like defaultOpenContent  be included in an html element? 

 

<defaultOpenContent

                                mode="interleave">

                                <any />

</defaultOpenContent>

 

Thank you.

Yours respectfully,

Robert (Bob) C. Leif, Ph.D.

Vice President

Newport Instruments

Email rleif@rleif.com

Web : www.newportinstruments.com