[
Lists Home |
Date Index |
Thread Index
]
John Cowan <cowan@mercury.ccil.org> wrote:
| Arjun Ray scripsit:
|
|> If this is acceptable, then my question is: What is the decision procedure
|> by which a generic parser-level filter could generate these views, if it's
|> to take namespaced names as a guide?
|
| This is a very interesting offshoot of architectural forms.
Actually, ArchForms are an offshoot of the general question here :-)
| Generally speaking the rule looks like: the HTML view converts non-HTML
| elements to their character data, whereas the books view rejects all
| non-books elements including their character data.
Well, this rule is asymmetric. It would require a *generic* parser-level
filter to have vocabulary-specific understandings. I'm interested in a
general rule - or equivalently, the requirements for a general rule.
| There would need to be some document that specifies this.
Well, part of the point here is to do it on the basis of instance markup
alone. Invoking external documents, to change the ground rules in the
interests of DWIM, is about the same as saying "if we had the schema for
the vocabulary...", isn't it?
|
