- From: José Manuel Cantera Fonseca <jmcf@tid.es>
- Date: Mon, 14 Jan 2008 16:04:59 +0100
- To: "Smith, Kevin, VF-Group" <Kevin.Smith@vodafone.com>
- Cc: Ubiquitous Web Applications Working Group WG <public-uwa@w3.org>
Hi Kevin, I totally agree wrt the Delivery Context functions !!! I was suggesting with my e-mail some work items that could be worth addressing in DIAL as language, independently of the DC functions. Best Regards Smith, Kevin, VF-Group escribió: > Hi José, > > To me the key driver to get a form of DIAL adopted is a standard delivery context API. This would likely take the form of a set of expressions which would be understood by compliant processors on servers (and potentially clients), and would hence allow portability of DIAL documents. As mentioned at [1], such an API would be based on the Delivery Context ontology, and could be bound to XSLT functions to allow a quick plug-in to existing documents. > > Cheers > Kevin > > > > [1] http://lists.w3.org/Archives/Public/public-uwa/2008Jan/0005.html > > -----Original Message----- > From: public-uwa-request@w3.org [mailto:public-uwa-request@w3.org] On Behalf Of José Manuel Cantera Fonseca > Sent: 14 January 2008 12:41 > To: Ubiquitous Web Applications Working Group WG > Subject: Short-Term DIAL Evolution > > > Hi all, > > I've been thinking on the short-term evolution of DIAL. The following > items are the result of a my own brainstorming, so feel free to discuss > them :) > > + Decoupling DIAL from XHTML 2 i.e base DIAL on different modules some > coming from XHTML 1 and some coming from XHTML 2. For example, the Role > and Access modules seem to be very stable but other XHTML 2 modules not > + Decoupling DIAL from DISelect (i.e. perhaps making DISelect an > optional module) > + Add some markup for simple policies, like pagination or layout (for > layout we can only address the minimum set of use cases needed for > mobile development and leave the generalization to the upcoming > Layered-UI XG) > + Standardize some values for something like the 'appearance' property > in CSS to map between the XForms controls and its concrete > representation. It is expected that the future Concrete UI Markup will > make this more general but we can start with a very simple spec > > What do others think? > > Best Regards > > > >
Received on Monday, 14 January 2008 15:12:00 UTC