• From: "Stephen Green" <stephengreenubl@g...>
• To: "Fraser Goffin" <goffinf@g...>, "noah_mendelsohn@u..." <noah_mendelsohn@u...>
• Date: Mon, 22 Oct 2007 14:22:28 +0100

In short there are two notable opposing forces resulting from the extension
and pruning methods we've discussed

A. the need to ensure to some extent that there is nothing essential in the
parts which will be pruned out by your application - a profiling mechanism
perhaps

B. the need to ensure that some method will exist to allow 'must
understand' to be
applied and properly handled even to something within an extension (which would
otherwise be pruned) - an exception mechanism perhaps

-- 
Stephen Green

Partner
SystML, http://www.systml.co.uk
Tel: +44 (0) 117 9541606

http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice

• References:
  • Re: The <any/> element: bane of security or savior of versioning?
    • From: "Stephen Green" <stephengreenubl@g...>
  • Re: The <any/> element: bane of security or savior of versioning?
    • From: noah_mendelsohn@u...
  • Re: The <any/> element: bane of security or savior of versioning?
    • From: "Stephen Green" <stephengreenubl@g...>
  • Re: The <any/> element: bane of security or savior of versioning?
    • From: Thomas Lord <lord@e...>
  • Re: The <any/> element: bane of security or savior of versioning?
    • From: "Stephen Green" <stephengreenubl@g...>
  • Re: The <any/> element: bane of security or savior of versioning?
    • From: "Stephen Green" <stephengreenubl@g...>
  • Re: The <any/> element: bane of security or savior of versioning?
    • From: "Fraser Goffin" <goffinf@g...>
  • Re: The <any/> element: bane of security or savior of versioning?
    • From: "Stephen Green" <stephengreenubl@g...>