RE: Content selection expressions

DISelect only specifies XPath. Keeping the technology within the scope of existing W3C technologies. Binding to EL is certainly a possibility. MobileAware has its own expression binding for a thematically similar technology, so we know from practical experience this is possible. From a high-level point of view, what is important is the ability to use selection within the content, so that the selection expressions can capture in some way the presentation requirements of the author. It is certainly within the philosophy to consider similar approaches in other domains. But mixing them might be a struggle. A DISelect processor that accepted EL instead of XPath would have additional features (such as bean access) and limitations (such as DOM access).

In terms of DISelect as specified, XPath is the language you use, and you can extend it to provide access to other contextual data if needed. For example, when DDWG eventually produces a vocabulary, someone could create an XPath binding to those properties so that DISelect would be able to use DDR data. (Yes, I think someone will implement that...)

I'm not tending one way or the other. Let's just see what evolves.

---Rotan.

-----Original Message-----
From: www-di-request@w3.org [mailto:www-di-request@w3.org] On Behalf Of José Manuel Cantera Fonseca
Sent: 18 October 2006 15:59
To: www-di@w3.org
Subject: Content selection expressions


Dear all,

Does the current version of the content selection  standard allow to include expressions in other languages than XPATH?  I'm thinking in expressions expressed in Expression Language (JSP 2.0) for example.

Thanks and Best Regards

Received on Wednesday, 18 October 2006 15:41:16 UTC