The first step is to obtain the XHTML M12N schemas. We'll create a directory structure as follows:
xH
xhtml11
xhtml11a
xhtmlm12n11
rdfa10
The XHTML M12N directory contains all of the modules for XHTML modularisation. Note that this doesn't mean we have a language--if we wanted XHTML 1.1 we'd need to go get the schemas for that from somewhere else. What we have are all the modules that can be used to create language such as XHTML 1.1.
Next we 'create' XHTML 1.1. This is just a driver file (xhtml11.xsd) and two further files, one of which lists all of the other schemas to include, and the other lists the models that are needed (i.e., groups, classes, etc.). These files are called xhtml11-modules-1.xsd and xhtml11-model-1.xsd, respectively. All three of these files are placed in the xhtml11 directory.
Next, we create a directory called xH10, and in it put driver and modules files. The modules file refers to all the normal XHTML schemas, except for cismap, hypertext and link. These need to be overridden so that the 'a', 'area' and 'link' elements don't have any of the attributes on them that will be coming from RDFa. Once this is done, we can add RDFa and then modify xhtml.Common.extra so that the attributes appear everywhere.
Our next RDFa 'rule' is to allow meta and link to appear anywhere. To achieve this we redefine xhtml.Misc.extra.
[Questions for Shane:
* when he comes to define XHTML 1.1 shouldn't the HTML element be in the driver file, and not in the model file?
* don't specify the location for schemas unless you have to
]
--- TEMP ---