You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by David Parker <dl...@facstaff.wisc.edu> on 2000/03/21 21:32:36 UTC
Creating a transformation into an
Attempting to grab the url attribute from a <ulink> node (DocBook XML file).
The click able text is added on at the end of the parent node <para>.
2. Focus and Scope:
This guideline is focused on the process-to-process exchange of structured
data (information objects). This approach is most applicable when the
exchanging partners retain different application software configurations
(for example, this guideline might not apply to exchange between two
systems based on similar Oracle databases). It is intended to stimulate
discussion about campus interoperability between technology planners and
managers, technologists and engineers responsible for implementing
exchanges of structured data.
This architecture for information object exchange is only one of several
potential solutions. Other approaches such as workflow and messaging
provide a richer set of functions for information object administration but
require much closer collaboration on software selection. Generic clients
such as web and/or TN3270 provide an only slightly reduced level of
autonomy but may be more difficult to integrate closely with a particular
business application. This guideline is not directed at workflow, messaging
or web clients. There is no intent, explicit or implicit, in this guideline
to constrain solutions for those environments. For more information about
these other areas please see the "Related Architectural Areas" section of
named Issues and Context for Implementing Process-to-process Exchange of
Structured Data. "Related Architectural Areas"Issues and Context for
Implementing Process-to-process Exchange of Structured Data.
XML file
------------------
<section>
<title> Focus and Scope:</title>
<para>
This guideline is focused on the process-to-process exchange of
structured data (information objects). This approach is most applicable
when the exchanging partners retain different application software
configurations (for example, this guideline might not apply to exchange
between two systems based on similar Oracle databases). It is intended to
stimulate discussion about campus interoperability between technology
planners and managers, technologists and engineers responsible for
implementing exchanges of structured data.
</para>
<para>
This architecture for information object exchange is only one
of several potential solutions. Other approaches such as workflow and
messaging provide a richer set of functions for information object
administration but require much closer collaboration on software selection.
Generic clients such as web and/or TN3270 provide an only slightly reduced
level of autonomy but may be more difficult to integrate closely with a
particular business application. This guideline is not directed at
workflow, messaging or web clients. There is no intent, explicit or
implicit, in this guideline to constrain solutions for those environments.
For more information about these other areas please see the
<ulink
url="http://www.wisc.edu/arch/results/proc_to_proc_iandc.html#OAA">
<citetitle>"Related Architectural Areas"</citetitle>
</ulink> section of named
<ulink
url="http://www.wisc.edu/arch/results/proc_to_proc_iandc.html">
<citetitle><i>Issues and Context for Implementing
Process-to-process Exchange of Structured Data.</i></citetitle>
</ulink>
</para>
</section>
XSL file
------------------
<!--================================================================-->
<!-- Template for the <ulink> tag -->
<!--================================================================-->
<xsl:template match="ulink">
<xsl:param name="link"><xsl:value-of select="."/></xsl:param>
<a href="{$link}">
<xsl:apply-templates select="citetitle"/>
</a>
</xsl:template>
<!--================================================================-->
<!-- Template for the <citetitle> tag -->
<!--================================================================-->
<xsl:template match="citetitle">
<xsl:value-of select="."/>
</xsl:template>
Re: Creating a transformation into an
Posted by David Parker <dl...@facstaff.wisc.edu>.
At 05:49 AM 3/22/00 -0500, you wrote:
>/ David Parker <dl...@facstaff.wisc.edu> was heard to say:
>| Attempting to grab the url attribute from a <ulink> node (DocBook XML file).
>| The click able text is added on at the end of the parent node <para>.
4. Issues and Context:
Compliance with this guideline leaves significant design and implementation
issues to be addressed. While important, these issues are not architectural
in nature and further discussion is contained in a separate document:
Issues and Context for Implementing Process-to-process Exchange of
Structured Data . The table of contents for that document is outlined
below. Issues and Context for Implementing Process-to-process Exchange of
Structured Data
From: Norman Walsh <nd...@nwalsh.com>
>I don't see what's wrong here.
>What does your template for para look like?
I think that you are right that it is in the call from <para>
but I do not have the experience yet, to understand why!
Thanks for the pointer to the http://nwalsh.com/docbook/xsl/ XSL DocBook
Stylesheets.
<!--================================================================-->
<!-- Use the <xsl:number> element to automatically number the -->
<!-- <section> tags. -->
<!--================================================================-->
<xsl:for-each select="//section">
<h3>
<xsl:number level="multiple" count="section" format="1.1.1. "/>
<xsl:value-of select="./title"/>
</h3>
<xsl:apply-templates select="./para"/>
</xsl:for-each>
<!--================================================================-->
<!-- Template for the <para> tag -->
<!--================================================================-->
<xsl:template match="para">
<p>
<xsl:value-of select="."/>
<xsl:apply-templates select="./itemizedlist"/>
<xsl:apply-templates select="./ulink"/>
</p>
</xsl:template>
<!--================================================================-->
<!-- Template for the <ulink> tag -->
<!--================================================================-->
<xsl:template match="ulink">
<xsl:param name="link"><xsl:value-of select="@url"/></xsl:param>
<a href="{$link}">
<xsl:apply-templates select="citetitle"/>
</a>
</xsl:template>
<!--================================================================-->
<!-- Template for the <citetitle> tag -->
<!--================================================================-->
<xsl:template match="citetitle">
<xsl:value-of select="."/>
</xsl:template>
Re: Creating a transformation into an
Posted by Norman Walsh <nd...@nwalsh.com>.
/ David Parker <dl...@facstaff.wisc.edu> was heard to say:
| Attempting to grab the url attribute from a <ulink> node (DocBook XML file).
| The click able text is added on at the end of the parent node <para>.
I don't see what's wrong here. I posted some additional comments to
the DocBook list [but I removed the crosspost; please don't crosspost
to the DocBook list]. What does your template for para look like?
Be seeing you,
norm
--
Norman Walsh <nd...@nwalsh.com> | Curiosity never killed anything
http://nwalsh.com/ | except maybe a few hours.