- From: Philip Fennell <Philip.Fennell@marklogic.com>
- Date: Wed, 19 Oct 2016 11:21:56 +0000
- To: Steven Pemberton <steven.pemberton@cwi.nl>, "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Hello Steven, I take it that it is referring to a text string of mark-up, when parsed as HTML(+XForms) and presented in the client, via an xf:output with mediatype = ‘text/html’, as part of the page that that mark-up may contain XForms elements too and if so whether the implementation should allow them access to the model contained within the parent page if they reference instances or binds defined in the parent’s model. Philip On 19/10/2016 11:38, "Steven Pemberton" <steven.pemberton@cwi.nl> wrote: By the way, I don't understand the second Note: When the media type is specified, implementations may handle the output content as presentation-only or as interactive content, and interactive content may be isolated from or capable of accessing the enclosing document that contains the output. Further implementation experience and user feedback is required. For example, if the output content includes XForms user interface elements, it may be desirable for them to access a default XForms model in the output content or from the enclosing document. Anyone able to enlighten me? Steven On Wed, 19 Oct 2016 12:33:48 +0200, Steven Pemberton <steven.pemberton@cwi.nl> wrote: > https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_output_Element > > As part of the re-treatment of @value (not yet complete), I have > re-written this section to make it clearer (and as it happens quite a > lot shorter). > > It was rather a lot of work, and I would appreciate it if you could > check it for me. > > Thanks. > > Steven
Received on Wednesday, 19 October 2016 11:22:27 UTC