[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: So maybe ID isn't a problem after all.

• To: David Brownell <david-b@p...>,David Carlisle <davidc@n...>
• Subject: Re: So maybe ID isn't a problem after all.
• From: Gavin Thomas Nicol <gtn@r...>
• Date: Tue, 13 Nov 2001 12:41:07 -0500
• Cc: xml-dev@l...
• In-reply-to: <095a01c16c12$50b90b40$6800000a@b...>
• Organization: Red Bridge Interactive, Inc.
• References: <9A4FC925410C024792B85198DF1E97E401C9B300@u...> <200111130008.AAA18294@p...> <095a01c16c12$50b90b40$6800000a@b...>

On Tuesday 13 November 2001 02:10 am, David Brownell wrote:
> Actually, there's the "how to maintain the links" problem too.
> When an author has gone to the effort to define IDs/anchors
> for use in linking, it's a lot more realistic to believe those IDs
> can be maintained over document evolution ... including the
> negotiated transformations that David Carlisle mentioned.

Acutally, the ID-ness here is orthoganal to the issue of link maintenance. 
Unique attribute values are important, not that the attributes be ID's.

> Since that's NOT true of XPath style addressing (navigating
> over a structure that usually changes between incarnations),

Depends on the XPath construct. You can match unique attributes using XPath 
too.

• References:
  • RE: So maybe ID isn't a problem after all.
    • From: "Champion, Mike" <Mike.Champion@S...>
  • Re: So maybe ID isn't a problem after all.
    • From: David Carlisle <davidc@n...>
  • Re: So maybe ID isn't a problem after all.
    • From: David Brownell <david-b@p...>

• Prev by Date: Re: Caught napping!
• Next by Date: Re: Caught napping!
• Previous by thread: Re: So maybe ID isn't a problem after all.
• Next by thread: Re: So maybe ID isn't a problem after all.
• Index(es):
  • Date
  • Thread