OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [dita] How much flexibility do specializers have to makeexceptions to behaviors that are outlined in the DITA standard?

On 10/25/07 2:41 PM, "Michael Priestley" <mpriestl@ca.ibm.com> wrote:

> Clarification:
> in the href overriding example, a processor might choose to create a
> preview by summarizing specialized elements in a target's <refsyn> or
> equivalent, rather than using the <shortdesc>. This wouldn't affect the
> syntax of the href, but does change the expected processing from the
> default.

What you've described is rendition, not address resolution.

That is, when I say "addressing" I mean "the object that is addressed by the
href value" which is different with what you do with that thing once you
have it.

That is, how or if you produce tooltips in some rendition is entirely a
matter of style. What those tooltips apply to (or at least what the initial
source of their ultimate value is) is a function of invariant address

That is, you can choose to produce or not produce tooltips, you can't change
what "mytopic.dita#topicid/elementid" means from an address resolution

[Note that this is one problem with DITA not using standard addressing
mechanisms: it provides no built in mechanism for choice in how you do
addressing at the fragment identifier level, which means you either have
non-DITA stuff or you use URIs that have to be interpreted by a specific URI
resolver. This is a fundamental problem with DITA 1.x that must be corrected
in DITA 2.]

> Main point remains the same: I think everything in "expected behavior" is
> expected default behavior; everything in "expected markup/syntax" is
> required unless otherwise stated. The syntax for href and conref should be

But the point is that that there are some things in DITA that are not
"expected behavior" but "required behavior", which includes, I assert, all
addressing and conref.



W. Eliot Kimber
Senior Solutions Architect
Really Strategies, Inc.
"Bringing Strategy, Content, and Technology Together"
Main: 610.631.6770

Sent using the Microsoft Entourage 2004 for Mac Test Drive.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]