- markup (76)
- xml (11)
- xslt (23)
- pipelines (8)
- atom (9)
- overlapping markup (6)
- schema (11)
- creole (5)
- dtll (1)
- xforms (1)
- xpath (1)
- xquery (2)
- coding (2)
- datagovuk (1)
- genealogy (4)
- hardware (1)
- linked data (15)
- named graphs (1)
- opendata (1)
- psi (3)
- skos (1)
- sparql (4)
- Talis (7)
- unicode (1)
- uri (4)
- versioning (1)
- visualisation (6)
- web (77)
- google (4)
- html5 (5)
- jQuery (2)
- rdf (45)
- ontologies (2)
- rdfa (8)
- rdfQuery (5)
- rest (6)
- wikis (1)
- work (3)
- legislation (2)
- xmlsummerschool09 (2)
- life (28)
- children (5)
- equality (6)
- gtd (1)
- environment (4)
- gadgets (5)
- software (3)
- xlinq (2)
- conferences (11)
- ukgc09 (1)
- xtech (9)
- xtech2008 (3)
- blog (8)
- drupal (3)
Recent posts
- 1 week 6 days ago
- 6 weeks 4 days ago
- 14 weeks 8 hours ago
- 15 weeks 2 days ago
- 15 weeks 5 days ago
Recent comments
- LuannFoley (not verified)
- Glass20Hilda (not verified)
- Anonymous (not verified)
- Landong Zuo (not verified)
- Herbert Van de Sompel (not verified)
Re: Essential Hierarchy
Even with the merged tags, I don’t think it’s really readable.
And I don’t see how the self-overlap case would work, unless every ancestor of the self-overlap elements also contained the numeric labels? Actually, I think you have to introduce a completely new way of thinking about XCONCUR: conceiving of a document as multiple hierarchies just doesn’t work for self-overlap.