- From: Erik Bruchez <ebruchez@orbeon.com>
- Date: Thu, 24 Apr 2025 20:16:21 -0700
- To: Steven Pemberton <steven.pemberton@cwi.nl>
- Cc: XForms <public-xformsusers@w3.org>
- Message-ID: <CAAc0PEUrWqmD1q8he1RD3ts393LxsQXVq0fS2_7TW9k4T1uH4w@mail.gmail.com>
If I recall correctly, one question was whether we could allow, or suggest, that not only simple content could be used, but possibly nested elements. For example: <data> <svg version="1.1" ...></svg> </data> <xf:output ref="data" mediatype="image/svg+xml"/> instead of having the SVG's XML escaped as text within the `<data>` element. I am not suggesting one way or the other at this point. -Erik On Thu, Apr 24, 2025 at 7:01 AM Steven Pemberton <steven.pemberton@cwi.nl> wrote: > Here is what we say already about <output/> for different media. It > already mentions HTML explicitly, and could cover SVG without change. > > The mediatype is obtained from the mediatype attribute if present, or > otherwise from the mediatype child element if any. > > If a mediatype has been specified, and the data to be output is non-empty, > the data is decoded or dereferenced depending on the base type of the data: > an xs:base64Binary value is base-64 decoded, an xs:hexBinary value is > hex-binary decoded, and an xs:anyURI value is treated as a URI and > dereferenced. For any other type, the data is used without modification. > Implementations should > <https://www.w3.org/community/xformsusers/wiki/XForms_2.0#intro-conventions> accept > at least image/* and, if the host language is some version of HTML, > text/html as possible values of mediatype. > > The data is rendered in a suitable way taking into account the datatype of > the value, the mediatype if any, the appearance attribute, and > localization and internationalization issues such as representation of > numbers and dates. > > Steven > > >
Received on Friday, 25 April 2025 03:16:37 UTC