I propose two changes for the markup used for the following Chiba output
extensions, in order to bring Chiba into alignment with existing W3C
Recommendations and Working Drafts:
1. Output as image
2. Output as anchor
1. Output as image
The current Chiba release provides this necessary functionality with the
non-standard output/@appearance='image'.
Extensions to appearance are allowed under XForms 1.0, but they must be
qualified names.
So, to be valid XForms this appearance attribute value should be
output/@appearance='chiba:image'.
However, it may make more sense to implement this function as
output/@mediatype='image/*' from the XForms 1.1 proposal.
In html-form-controls.xsl change
<xsl:when test="@xforms:appearance='image'">
to
<xsl:when test="@xforms:appearance='image' or
starts-with(@xforms:mediatype, 'image/')">
Note: Implemeneting the Qname of "chiba:image" is harder because it
requires parsing the attribute value and matching the prefix to
namespace declarations in scope in the document(), another point in
favor of simply using the XForms 1.1 WD @mediatype attribute, even if it
is not yet a Recommendation.
2. Output as anchor
The current Chiba provides this necessary functionality with the
non-standard output/@appearance='anchor'.
Extensions to appearance are allowed under XForms 1.0, but they must be
qualified names.
So, to be valid Xforms this appearance attribute value should be
output/@appearance='chiba:anchor'.
It may make more sense to implement this function as
output/@mediatype='image/*' from the XForms 1.1 proposal.
Implement partial Xlink support on output with
output/@xlink:type='simple' when there is no xlink:href present.
This idea is due to Kenneth Sklander, and is based on the Xlink
recommendation, which lists xlink:type as the only required attribute.
XLink purists may object that a link without a lexically visible URI is
not discoverable; however, it is at least declared as a link, and I
doubt they would be happy with @appearance="chiba:anchor" declaring
something to be a link.
I have also proposed to Mozilla Xforms that they implement Kenneth's
interpretation of XLink, as their user agent also has partial XLink
support. I don't see any interaction with the XForms recommendation
here, as foreign namespaced attributes are already allowed, so I believe
that this is ready to go.
In html-form-controls.xsl change
<xsl:when test="@xforms:appearance='anchor'">
to
<xsl:when test="@xforms:appearance='anchor' or
(@xlink:type='simple' and not(@xlink:href))">
Leigh L. Klotz, Jr.
Xerox Corporation
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
|
