Hi Kate,
My reading of the XLink spec is that show="embed"
is *not* the same as a transclusion mechanism like XInclude. The paragraph
in the spec after the one you quoted says:
"Just as for the HTML IMG element,
embedding affects only the presentation of the relevant resources; it does not
dictate permanent transformation of the starting resource. Put another way, when
an embedded XLink is processed, the result of styling the ending resource of the
link is merged into the result of styling the resource into which it is
embedded. By contrast, when a construct such as an XInclude element [XInclude] is resolved, the original XML is actually
transformed to include the referenced content."
This means the referenced content is styled as an
isolated piece and the formatted result embedded in the format of the calling
document. That is different from copying the XML of the referenced
content into the context of the current document and then applying a stylesheet
to the resulting document. The formatting of the XLink'ed content
could not rely on any context of the calling document. I think that would
work as expected for some elements but not others.
However, if it works for your use case, all
you need is a customization to implement it.
----- Original Message -----
Sent: Thursday, February 04, 2010 11:35
AM
Subject: [docbook] xlink: show
embed
I'm confused about the
attribute xlink:show and the option embed. On one hand, the xlink:show
attribute appears to describe what
should happen when you click the link in the built document (e.g., when you
click the link, a new window should open, etc.,). And yet on the other hand, the embed option suggests
transclusion (http://www.w3.org/TR/xlink/).
If you had a guilabel, that used
the xlink:href attribute along with xlink:show="embed", does this mean that
the guilabel element would be replaced
by the element that it is pointing to?
Thank you, Kate
xlink:show
Identifies the XLink show behavior of the link.
new An application traversing
to the ending resource should load it in a new window, frame, pane, or other
relevant presentation context. replace
An application traversing to the ending resource should load
the resource in the same window, frame, pane, or other relevant presentation
context in which the starting resource was loaded. embed An application
traversing to the ending resource should load its presentation in place of the
presentation of the starting resource. other The behavior of an application
traversing to the ending resource is unconstrained by XLink. The application
should look for other markup present in the link to determine the appropriate
behavior. none The
behavior of an application traversing to the ending resource is unconstrained
by this specification. No other markup is present to help the application
determine the appropriate behavior. ..........................................................................................................................................................................................................................
| Kate Wringe | Tech
Writer 2| Sybase 445 Wes Graham Way, Waterloo, ON, N2L 6R2 Canada |
Tel: (519) 883-6838 | kate.wringe@sybase.com | www.sybase.com
|
|