backward-compatibility of languages (aka forward compatibility)

Have you or the TAG addressed the Web Architecture principal that
languages should be specified so that future versions of the language
can work (with gracefully degraded functionality) with old software
systems?  This may be an open-systems thing; traditional "backwards
compatibility" goes the other way, allowing new software to work with
old data.  HTML's "ignore tags and attributes you don't know about"
was the embodiment of this principal, and probably was essential to
the web (although it was also a pain).  

I think RDF has perfected this, but at some costs.   Peter's paradox
is one of the costs.   While I am defining the safe territory and
costs of crossing into the badlands, I want a good statement of this
principal to explain why we're here in the first place.

    -- sandro

Received on Sunday, 30 June 2002 09:56:11 UTC