extensibility and versioning

16
Versioning and Extensibility Paul Downey March 2005

Upload: paul-downey

Post on 17-Jun-2015

781 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Extensibility And Versioning

Versioning and

Extensibility

Paul DowneyMarch 2005

Page 2: Extensibility And Versioning

COBOL COPYBOOK

005900* GRACE HOPPER MAY RULE, 005901* BUT I'M NO CARD WOLLOPER006000 01 CUSTOMER-PROFILE.006100 05 FIRST-NAME PIC X(26).006200 05 LAST-NAME PIC X(26).006300 05 ADDRESS PIC X(300).006400 01 ADDRESS-ALL REDEFINES ADDRESS.006500 10 LINE-ONE PIC X(20).006600 10 LINE-TWO PIC X(20).

Page 3: Extensibility And Versioning

Type-Length-Value (TLV)

Page 4: Extensibility And Versioning

MUST IGNORE RULE

Page 5: Extensibility And Versioning

TOOLS

Page 6: Extensibility And Versioning

Interface Description Language

Page 7: Extensibility And Versioning

Mine!

http://heyhowdeyhey.com/mine/

Page 8: Extensibility And Versioning

PIPES

Page 9: Extensibility And Versioning

Meanwhile on the INFORMATION SUPERHIGHWAY

Page 10: Extensibility And Versioning

�������� �����

� �

marquee>All your base are belong to us</marquee

<script>window.open ("http://www.some-dodgy-website.tld",

"hey-click-on-this-popup"); </script>

<blink>HOW ANNOYING AM I?</blink>

<img src=“another-picture-of-my-cat.gif”>

Page 11: Extensibility And Versioning

XML / XHTML

Page 12: Extensibility And Versioning

<?XML?>

Page 13: Extensibility And Versioning

XML

Page 14: Extensibility And Versioning

Namespace Pipe Works

Page 15: Extensibility And Versioning

No Future

Page 16: Extensibility And Versioning

Dear W3C, I would like:

MUST IGNORE to be anointed

Namespaces for ownership of a set of names not version control, as originally intended

Means of communicating a break in compatibility e.g. MUST UNDERSTAND

Descriptions to enable evolution naturally