MHonArc v2.5.0b2 -->
dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [dita] RE: [Dita-ot-developer] Handling of xref attributes
From: Michael Priestley <>
To: "Paul Prescod" <>
Date: Thu, 9 Feb 2006 19:59:31 -0500
scope="local": grab linktext
(and shortdesc if available) from the target unless defined in the link/topicref/xref
-
format is assumed to be dita, href will change .dita to .html on output;
if format not dita, linktext must be defined in the link/topicref/xref
scope="peer": linktext must
be defined in the link/topicref/xref (shortdesc optional)
-
format is assumed to be dita, href will change .dita to .html on output
scope="external": linktext
defaults to the URL unless defined in the link/topicref/xref (shortdesc
also optional)
-
format is assumed to be NOT dita; href will be passed through as-is
Michael Priestley
IBM DITA Architect
Classification Schema PDT Lead
"Paul Prescod"
<>
02/09/2006 07:52 PM
To
Michael Priestley/Toronto/IBM@IBMCA
cc
<>,
<>, "Robert D Anderson"
<>, "Su-Laine Yeo" <>
Subject
RE: [dita] RE: [Dita-ot-developer]
Handling of xref attributes
From: Michael Priestley [mailto:]
Sent: Thursday, February 09, 2006 4:14 PM
To: Paul Prescod
Cc: ; ;
Robert D Anderson; Su-Laine Yeo
Subject: Re: [dita] RE: [Dita-ot-developer] Handling of xref attributes
Re the scope attribute: the current definition is this:
The scope attribute identifies the closeness of the relationship between
the current document and the target resource.
- Set scope to local when the resource is part of the current set of content,
and should be accessed and copied to the output directory.
Okay, this one is relatively clear.
- Set scope to peer when the resource
is part of the current set of content but is not accessible at build time.
What does that mean for software? What does
an implementation _do_ when it sees this attribute.
- Set scope to external when the resource
is not part of the current information set and should open in a new browser
window.
What does this mean for my print deliverables?
Re:
>Having components authored by other people is the norm in topic oriented
>authoring. If it is part of your "information set" then the
momentary
>unavailability of the information strikes me as a transient problem
that
>should be reported as a warning. If I shut up the warning by setting
the
>scope attribute to "peer" then I'll never fix my problem
before
>publishing.
If it's a transient problem you wouldn't set scope="peer" you'd
set scope="local". But if it's an ongoing situation (like, for
example, you are publishing a component of a website, and someone else
from another company is publishing another component) then while you are
part of different publishing streams you are converging on the same deliverable,
and want the output to act integrated even though some of the info has
to be "faked" at build time. That's when you set scope="peer".
I hope that clarifies.
But what do I put in my DITA href to make
this situation "work" and what should a DITA publishing tool
do with that href? And how is the behaviour of the DITA tool different
if I use scope="peer" versus scope="external"? Just
in the way that the windows work in a browser?
Paul Prescod
References:
RE: [dita] RE: [Dita-ot-developer] Handling of xref attributes
From: "Paul Prescod" <>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
