[
Lists Home |
Date Index |
Thread Index
]
I missed the original thread, but reckon this is a marvellous idea. Recently
I was doing some SVG work and found the 'real' published interfaces (Java &
ECMAScript) in the spec really useful for pinning down the 'how', without
complicating the 'what' in the text. I'm pretty sure that this benefit would
transfer nicely to the spec 'published interface' idea.
My only worry would be an artifact corrsponding to something in the real
interfaces, where in a particular implementation one might encounter 'not
yet implemented' messages much later than one would really like (in Batik
this sometimes happened in runtime errors). Translating this to the spec
interface, I guess the answer would be some form of reality-checking
mechanism, so that new specs weren't relying on 'interfaces' that were
underdefined.
Cheers,
Danny.
-----------
Danny Ayers
Idea maps for the Semantic Web
http://ideagraph.net
<stuff> http://www.isacat.net </stuff>
Semantic Web Log :
http://www.citnames.com/blog
>-----Original Message-----
>From: Eric van der Vlist [mailto:vdv@dyomedea.com]
>Sent: 26 October 2002 10:26
>To: xml-dev@lists.xml.org
>Subject: [xml-dev] [Fwd: Defining "public interfaces" in specifications]
>
>
>FYI, since this is extending an idea first posted here :-)
>
>Eric
>
>--
>Curious about Relax NG? My book in progress is waiting your review!
> http://books.xmlschemata.org/relaxng/
>------------------------------------------------------------------------
>Eric van der Vlist http://xmlfr.org http://dyomedea.com
>(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
>------------------------------------------------------------------------
>
|
