to list ... 1. Validation body.xsl Line 529 The attribute name changed from "name" to "id" From the XHTML DTD - "The destination(or link 'target') is identified via its 'id' attribute rather than the 'name' attribute as was used in HTML." 2. RDF Validation header.xsl Line 278 Provenance simplified The MeSH style CURIE was flattened as it was found that the W3C RDF Validator failed to produce a graph. The [dcterms:provenance] was only printed if a <meta:printed-by /> and <meta:print-date /> was present. If a Literal is inadequate for processing, the "Print Publisher" or, for example, [dcterms:dateSubmitted] can be expressed in the user defined meta data fields. 3. Validadation / Display body.xsl Line Line 769-812 (no changes) The display of maths depends heavily upon links to CSS with functions added via XSL. The links necessary are not built into the Transform. Note to users: Here is your chance to fiddle with it - you know you want to. That said, the validation of imbedded formulae has no problem, although the name space (MathML 1.01 vs. MathML 2.0) might cause problems in some applications, nor does the PDF output have any display irregularities. Future Directions It seems to me, and from all reports me alone, that HTML seen as an Object has an implied "self" RDF subject that is encapsulated in the <head> only. Therefore it is mostly improper to mix meta data by referencing other documents (also with a "self") in the <head>. There are exceptions, links to schema, links to original sources etc., but in the main, there exists no natural ontology to sort out semantics after the mixing. Web surfing is not Reasoning, for now anyway[a]. The transform markup is clean, and easy to read and edit by hand. I see no reason why RDFa should not be used to clarify meta data in the <body> of a document. The extra name spaces do interfere with DTD validation though. There is a transform to extract RDF XML triples from XHTML, and RDFa permits the development of hierarchies[b]. There is one school of thought, again I might be the only student, that says bibliographic references are a display for document ideas just as MathML is a display for mathematical ideas. So, why not embed MODS (Meta Data Objects) just like MathML. MathML is Entity intensive and less amenable to schema processing, so in fact this project is easier[c]. References [1] PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN" <http://www.rustprivacy.org/may.pdf> <http://www.rustprivacy.org/may.odt> [2] W3C RDF Validator <http://www.w3c.org/> GRDDL <link rel="transformation" href="http://xml.openoffice.org/odf2xhtml/rdf-extract.xsl"; /> [3] *.odf/content.xml PUBLIC "-//OpenOffice.org//DTD Modified W3C MathML 1.01//EN" <http://www.rustprivacy.org/UniversalMath.pdf> <http://www.rustprivacy.org/UniversalMath.odt> [a] <http://www.rustprivacy.org/> [b] <http://www.w3.org/TR/2008/NOTE-xhtml-rdfa-primer-20081014/> [c] <http://www.loc.gov/standards/mods/> <http://www.rustprivacy.org/FunForLibrarians.pdf> <http://www.rustprivacy.org/PIIandMODS.pdf>
--- On Thu, 12/4/08, Gannon Dick <[EMAIL PROTECTED]> wrote: From: Gannon Dick <[EMAIL PROTECTED]> Subject: Re: [xml-dev] Re: [odftk-dev] odf2xhtml To: [email protected] Date: Thursday, December 4, 2008, 6:30 PM I'll post the patch over the weekend.
