Re: Examples

> I'm not saying that you must customize DTD and add new element. But this > approach has benefits over role="xxx" tweaking. Well, it is much nicer, to add a new element, but... > Only drawback is that > your documents would not be DocBook DTD compliant. But if you don't send > your source document outside of phpdoc group there wouldn't be problems > with it. Let's imagine we would like to make a cool book format of the phpdoc files. Then we may use the style sheets used by O'reilly, but if we add tags, and this goes on, we were unable to work with third party tools supporting DocBook. With a role attribute we can specify that this is a seealso para. For style sheets not customized for this role, that would be a normal _para_. For style sheets not customized for a new tag, that would be a _problem_... We can't clearly state, that the docs would strictly stay here, and would only be processed by our scripts. IMHO it is the best way to stay on the way of world standards, and so we are staying open to any standard tools and programs. NameSpaces and Schema will be a good way in the future, to elegantly handle such situations, while staying compatible, but as seen, we have no possibility to make a really elegant decision. In my viewpoint defining that role is the best we can do here. Goba