> You and I disagree about whether an enhancement in BD that isn't > implemented in CF represents an incompatibility
Excuse my jumping in. If I'm not mistaken, one area of contention here is whether when BD adds a tag that cf doesn't support, it should be prefixed with 'CF' or 'BD'. It's arguable both ways IMO. Using BD ensures that it won't conflict with future cf tags. However, Adobe/MM is obviously aware of BD, and I'd guess it's pretty likely that they'd either make their new tag compatible with the existing DB one, or use a different name. Also, using BD permanently flags the tag as having originated with BD, which IMO isn't a useful semantic distinction. In any event, this doesn't seem like it should be a major source of friction. Dave Merrill ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
