- markup (52)
- xml (7)
- xslt (21)
- atom (8)
- overlapping markup (2)
- schema (9)
- creole (4)
- xforms (1)
- pipelines (7)
- coding (2)
- dtll (1)
- genealogy (3)
- gtd (1)
- hardware (1)
- legislation (1)
- ontologies (2)
- unicode (1)
- web (24)
- google (3)
- rdf (6)
- rest (3)
- wikis (1)
- work (1)
- xpath (1)
- xquery (1)
- xtech2008 (3)
- life (26)
- children (5)
- equality (6)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (7)
- xtech (6)
- blog (7)
- drupal (3)
Re: XTech 2007: Wednesday 16th May Afternoon
I think you’re misrepresenting XSD a bit. There’s no requirement for tight-coupling in systems that use XML Schema. They provide the
xsi:schemaLocationattribute if you want to specify the schemas that can be used to validate a document, but that certainly doesn’t preclude you from validating that document against other schemas.The way XSD developers think is that you have a pool of schemas that are associated with namespaces, and in each of them you provide wildcards that indicate where content from other namespaces can go (and what kind of validation you want for that content). If you want your XHTML to contain RDF, SVG and MathML then make sure you design your XHTML with wildcards to indicate where elements from foreign namespaces can go, and provide the pool of XHTML, RDF, SVG and MathML schemas to the validator.
I’ll have to blog separately about the difference between Creole’s and NVDL’s approaches…