It’s just data

Getting to Xen

Erik Meijer: For example given a bibliography of books, bib, we can select all books whose publisher is Addison-Wesley that are published after 1991 by the following filter expression.

book* AWbooks =[it.publisher == "Addison-Wesley" && 
            it.year > 1991];

Sweet!  Note the use of * to denote sequence, and the implicit it variable.  There also are embedded expressions and apply-to-all.

Missing, or incompletely described at this point, are namespaces and mixed content.

[via Dare Obasanjo]

RE: Getting to Xen

  The link you provided doesn't seem to be working in IE. I guess this is to make up for the fact that Erik's original link only works in IE :)

Anyway as for the stuff you feel is incompletely described or missed completely like namespaces and mixed content, I'd like to point out that Xen's goal was to create a way to manipulate what people consider to be data-oriented XML as opposed to document-oriented XML (I give better descriptions of these concepts in There are known gaps in the story and some of this is stuff I'd like to see end up in the .NET Framework as opposed to remaining research work so I'm definitely actively involved in seeking solutions to these problems. Mixed content is particularly problematic, Erik and I have talked about how one would actually deal with them in a reasonable fashion to some degree but haven't sketched out anything concrete.

With Whidbey (.NET v2.0) ship work winding down and Orcas (post .NET v2.0) not yet started I'll be able to spend more time thinking about these problems and perhaps putting together a paper of my own.

I'm glad you found it interesting.

Message from Dare Obasanjo at

Dare: namespaces are certainly relevant to data-oriented XML.  I also personally believe that the line between data oriented and documented oriented is as illusionary as the line between metadata and data.

If the discussions you describe are open to outside participation, I'm interested.  In any case, I'll be sure to look Erik up at the xmlconference.

P.S.  I fail to see anything wrong with the URLs I provided... they seem to be properly URL encoded.  Any idea as to why they confuse IE?

Posted by Sam Ruby at

Dare: speaking of mixed content, have you considered posting your messages as xhtml:body or atom:content?  If your application already 'groks' XML, then I wouldn't have to guess as to the formatting.  Often getting it wrong, such as in the botched hypertext link in your comment.

There is no reason why you couldn't continue to include description in the entry in support of clients which only are looking for that element...

Posted by Sam Ruby at

Web ready structured objects

Interesting study on how to adapt OO language syntax to make a language support something similar to XML Schema natively...... [more]

Trackback from Notes from Classy's Kitchen


I get the following error when I try to click any of the links

"Parameter entity must be defined before it is used. Error processing resource ''. Line 85, Position 2


This seems to be related to a known bug in the XML parser that ships with IE [I have no idea if and when it will be fixed]

The discussions are currently internal (IP fiercely guarded and all that crap) but I wouldn't mind talking about this informally at XML 2003 [if management lets me attend].

RSS Bandit doesn't currently allow rich text editing so I have no reason to send xhtml:body. I can try writing <a> tags next time I want to provide a link.

Posted by Dare Obasanjo at

Expando properties

Don Box:  If you look at  JScript.Net, you will find a  fourth one.  And a compelling motivation for unification... [more]

Trackback from Sam Ruby


Add your comment