As opposed, say, to making sure two specifications can specifically collaborate, for example XHTML and XForms.
-Erik
Eric van der Vlist wrote:
I'd like to show only links corresponding to the credentials of the current user.
To make that as flexible as possible, I have thought of describing the roles needed by the different pages in a XML document and the format could be something such as:
<page id="admin" role="administrator" path="/administration"/>
The basic idea is that instead of directly using xhtml:a links, Models and/or views would include elements such as : <l:a ref="admin">administration</l:a> and this would be replaced by the corresponding link depending on the credentials in the epilogue.
Now, wouldn't it be nice if this information was in my page-flow.xml?
That would actually be easy to do if the schema of the PFC vocabulary was opened and allowed foreign attributes (and eventually foreign elements in complex content elements).
I could then write in page-flow.xml:
<page id="admin" path-info="/administration/" view="admin-view.xsl" foo:role="administrator"/>
and centralise the descriptions of the pages in a single document.
There are probably many other uses of such a flexibility and I think that this is something that could probably be generalised...
Of course, I could already achieve something similar using PIs:
<page id="admin" path-info="/administration/" view="admin-view.xsl"> <?foo role="administrator"?> </page>
Buts that's a poor man's hack that do not really use PIs for what they've been created for...
Eric
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
