dita — archive

[Bruce Nevin]

I guess I don't understand the reason for using regular expression syntax to describe the syntax for entering an attribute value in a specialization. Does some tool for creating domain usage declarations require regular expressions as input? Is XSL pattern matching required? What audience is the regular expression syntax directed to, and for what purpose? Wouldn't it be more straightforward to say each parenthesized module ancestry specification is a space-separated sequence of module names beginning with the root module name (topic or map) and ending with the name of the module whose ancestry is being declared? (The phrase "parenthesized module ancestry specification" occurs just prior to this definition.) Jeff said something similar: > It doesn't fully describe the domains attribute value since > attribute domain declarations take the form: > a(module1 moduleN) > where module1 is always either "props" or "base". (But did you mean "where module1 is always either "topic" or "map"? And I don't understand the leading 'a', or did you mean a=(module1 moduleN)?) Robert added: > I wonder if it might be clearer if the example also allowed (topic pr-d), > the programming domain; the topic then contains 3 domains coming off of topic, > and one domain that further specializes one of those three. It would be just as informative to point out that the example includes cpp but excludes pr-d as a whole. But my question on reading this is, having declared pr-d, why would I want to still declare cpp-d? All the elements in cpp-d are already available as part of pr-d, aren't they? Is the ancestry of pr-d not recoverable from that of cpp-d? /Bruce >