dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Archspec "linking" section
- From: "Park Seth-R01164" <seth.park@freescale.com>
- To: "DITA TC" <dita@lists.oasis-open.org>
- Date: Sun, 12 Jul 2009 09:00:46 -0700
I'm reviewing the ID
att section, which covers a lot of information that should be more appropriately
described in a "linking and referencing" section as we discussed a couple of
weeks ago. I feel we need
to create this topic and make a clear distinction
amongst:
- The ID attribute is
required to make an element eligible for link participation (and perhaps other
purposes, such as search). [covered in ID attribute section][see "linking and referencing" for how ID attributes are used in
linking]
- Links require a
certain syntax that--in the case of targeting elements within a
topic--requires a fragment identifier syntax that is non-conformant with
Xpointer. [covered in "linking and referencing
section]
- When a link is
established, the link behavior depends on the following
items... [covered in "linking and referencing section; provide
the following links to appropriate sections]
- the element that
contains the link attribute (topicref/mapref have certain restrictions)
[see
topicref/mapref]
- the attribute
that contains the link (href vs. conref) [see
href/conref]
- conaction and
conrefend attributes values (for conref only) [see conref]
- target type (dita
vs. non-dita) [see format attribute]
- Indirect linking
(keyref) enables the ability to call indirection targets (which are defined
elsewhere directly) using a key string. [see
keyref]
Can we get the
"linking and referencing" section in place, in a couple
days?
--------------------------------------------
seth park
information architect
Freescale Semiconductor,
Inc.
512.895.2463
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]