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

Re: XML feature manifest/profile (was RE:: Re: deter

• To: xml-dev@l...
• Subject: Re: XML feature manifest/profile (was RE:: Re: determining ID-ness in XML )
• From: Gavin Thomas Nicol <gtn@r...>
• Date: Sat, 24 Nov 2001 11:26:39 -0500
• In-reply-to: <9A4FC925410C024792B85198DF1E97E401E63002@u...>
• Organization: Red Bridge Interactive, Inc.
• References: <9A4FC925410C024792B85198DF1E97E401E63002@u...>

> And that's the problem I was scratching at with:
> "5) Refactor the various specs so that they layer cleanly, and add some
> sort of "features" or "profile" string to negotiate the feature set
> between the processor and the application."
> http://lists.xml.org/archives/xml-dev/200111/msg00794.html

I tend to be against this, mostly because people and the processors will 
almost certainly not negotiate cleanly. If you're worried about there being 
so many variations on a theme, you're better off contraining the input to
reduce the number of combinations.

In other words, I'd remove features (like ID!) from XML entirely, or remove 
them from the model (like Entity boundaries) before giving people an 
*optional* way of processing them.

• References:
  • XML feature manifest/profile (was RE:: Re: determining ID-ness in XML )
    • From: "Champion, Mike" <Mike.Champion@S...>

• Prev by Date: Re: Re: determining ID-ness in XML
• Next by Date: RE: Re: determining ID-ness in XML
• Previous by thread: XML feature manifest/profile (was RE:: Re: determining ID-ness in XML )
• Next by thread: Sharing Techniques: White Spaces in HTML pages by XSLT
• Index(es):
  • Date
  • Thread