[Home] [By Thread] [By Date] [Recent Entries]
I found I needed to add a namespace to get 'oXygen' to use a MicroRNG RelaxNG schema, then it was OK. So <grammar xmlns="http://relaxng.org/ns/structure/1.0"> <start> ... validated some MicroXML just fine in oXygen 11.2 but only with the namespace included. It didn't work (v11.2) with just <grammar><start> ... It was the need for a namespace which caused problems with a lightweight W3C XML Schema. If MicroXML only includes the xmlns and treats it as just an attribute and doesn't support prefixes then I would want to be able to have my MicroXML W3C XML Schema (subsetted) start with <schema xmlns="http://www.w3.org/2001/XMLSchema">... but this causes problems with tools which seem to expect <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">... - presumably something to do with the W3C XML Schema spec? ---- Stephen D Green ---- Stephen D Green On 24 December 2010 11:02, Dave Pawson <davep@d...> wrote: > On Fri, 24 Dec 2010 09:16:05 +0000 > Stephen Green <stephengreenubl@g...> wrote: > So how 'easy' would it be to include this in >> validating MicroXML parsers (if there ever are such things)? Perhaps >> easier than having to implement something like XSD which isn't valid >> as XSD; perhaps less risky anyway. > > This is a schema, so I can use it today, > with nxml-mode/emacs for editing, > with Jing for validating. > > Not sure what more I'd need? > > > -- > > regards > > -- > Dave Pawson > XSLT XSL-FO FAQ. > http://www.dpawson.co.uk >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |

Cart



