Just-In-Time-Trees (JITTs): Next Step in the Evolution of Markup?. Durusau, P. & Brook O'Donnell, M. In
abstract   bibtex   
Recording multiple possible encodings for a text has been treated as a problem of syntax (CONCUR, milestones, stand-off markup, Bottom-Up Virtual Hierarchies, Layered Markup and Annotation Language, MECS/TexMECS, etc.) and as a problem of parsing (Earley's algorithm, active chart parsing, tree-adjoining grammars). While offering various advantages and shortcomings, these efforts fall short of isolating the fundamental difficulty that gives rise to the problem. The simple tree model, which XML enforces, is a symptom and not the cause of this problem. Descriptive markup divides texts into content and markup. Or as previously stated by the authors, "Markup is metadata about #PCDATA." The fundamental problem is that all prior methods treat markup as static trees of metadata about #PCDATA. If that changes to: Trees are assertions about metadata, the fundamental difficulty of representing multiple trees in a single document instance resolves into a processing issue.
@inproceedings{ dur02,
  crossref = {xmarkup2002},
  author = {Patrick Durusau and Matthew {Brook O'Donnell}},
  title = {Just-In-Time-Trees (JITTs): Next Step in the Evolution of Markup?},
  topic = {jitt[1]},
  uri = {http://www.sbl-site2.org/Extreme2002/JITTs.html},
  abstract = {Recording multiple possible encodings for a text has been treated as a problem of syntax (CONCUR, milestones, stand-off markup, Bottom-Up Virtual Hierarchies, Layered Markup and Annotation Language, MECS/TexMECS, etc.) and as a problem of parsing (Earley's algorithm, active chart parsing, tree-adjoining grammars). While offering various advantages and shortcomings, these efforts fall short of isolating the fundamental difficulty that gives rise to the problem. The simple tree model, which XML enforces, is a symptom and not the cause of this problem. Descriptive markup divides texts into content and markup. Or as previously stated by the authors, "Markup is metadata about #PCDATA." The fundamental problem is that all prior methods treat markup as static trees of metadata about #PCDATA. If that changes to: Trees are assertions about metadata, the fundamental difficulty of representing multiple trees in a single document instance resolves into a processing issue.}
}

Downloads: 0