developers hate xml
- the slides are multi-colored and white, and the content is very sparse -- I love it. He and Don both use the same format.Numbered below
1. What is Xml?
2. XML is the UNIVERSAL DATA FORMAT
3. XML IS CARDBOARD
- references Pat Helland's Metropolis speech - alludes to xml being "Cardboard" - need something to ship the goods around in
- Xml isn't the important part, xml is the container for the goods
4. ???
5. XML processing is an island
6. [XSLT
XmlDocument
XmlReader
E4X]
[Chris Anderson has a slight, but well-tamed lisp]
7. applications to do more than process xml
integrated programming models are key
(see my upcoming panel question)
8. XML vs. .NET
9. (Schema, Loose, Xml type system) venn diagram (metadata, strong, clr type system)
- huge disparity between the two -- impedance mismatch
- difficult to do implementation inheritance in XML :)
10. ???
11. Applications integrate with XML
- it's not that xml is the heart of your system, it is the plumbing
Don: "Isn't most development just integration? I mean, not all of us have the luxury of 'greenfield' development like the Avalon team."
ChrisAn - Chatty protocols are bad, explicit boundaries between services.
Don"Take Technorati - prolly not much code, it's about the data" (paraphrased)
ChrisAn "Ok, Let's talk about OLAP - guessing that they have some OLAP (Tim Bray "It's a big honkin MySql database. They do all of it Perl." Sam Ruby "No, there's some Python, php, and [garbled]."
ChrisAn -- "Let's move on."
12. XAML
13. Why did we create XAML.
- xml is a great way to integrate.
XAML is a protocol for working between graphic designers and developers (Er???)
14. What about XML?
-
15. What is the developer experience?
The programming model should dictate the markup
16. Markup = OM
Core tenet of Avalon design: The markup reflects the object model.
Agree with Tim that Xml/Object mapping is not
17. Tag = instance
18. Attribute = Property | Event
19. Property Tag (sample)
Attribute promotion
Opens up the floor - "What should we have done?"
Don recommends "Change 'tag' to 'thingy'"
Why did you not use SVG? (you GD microsoft MOFOs, why did you yet again invent a new standard."
SVG is great for doing vector markup.
XUL - to do the UI markup
HTML - text markup
Wanted a single platform to do everything - d'oh -- [ commentary - what about DSLs and orthogonality and intentional programming and keith short's software factories]
Interesting question - "Why Button.Background rather than *just* background" - need to distiquish between properties and the types of the objects that are instantiated and assigned to the properties.
<Button>
<Button.Background>
additional cruft
</Button.Background>
</Button>
preferred way of doing things is to have a XAML file and a partial
XML Namespace == Assembly + CLR Namespace
Programming model is .NET
- XAML is a 'general purpose' .NET centric serialization format that is not coupled to xml schema.
Developers don't hate XML
they hate the systems that force XML to be more than data
XML is your data
[Scott Hanselmann looks less like a puppy in person]
"If you don't know where it's been, be careful how you love it."
"I hope that there is going to be a rich ecosystem of tools around XAML"
"Trying to create a runtime that emulates something we haven't shipped is a bad thing."
Chris Sells had a nice Camel cigarette knock-off tshirt - XAML: Smooth and Satisfying"
Comments