I'm writing to my brother about go-karting in Montreal last night, but OS X Mail editor doesn't grok hypertext. I'm tired of in-your-face URIs and poor-man's hypertext. The thunderbird editor groks hypertext but doesn't know that integrity is job one. I really should check that this bug is reported and report it if not, but I don't want to manage yet another bugzilla account. Oh for OpenID in bugzilla! I also want to make sure the lack of "treat this as plain text" in firefox is a reported bug.
Via Karen in the TAMI project, I gather last month the Department of Justice and the Department of Homeland Security announced the result of an XML collaboration - version 0.1 of the National Information Exchange Model (NIEM) which will be used for law enforcement, emergency management, etc. communities and the parties who exchange information with them.
I hope to check it out. Better yet... I hope somebody else checks it out and writes a GRDDL transformation.
Somebody listed SAML+XACML as an access control model, and I asked for a summary, as contrasted with the unix user/group/world model. The summary was, XACML is an access control rules language; you can write rules about access and credentials. So I'm taking a look at XACML
section 3.3 Policy language model looks nice... it's a UML diagram; pretty straightforwardly translated to OWL
reading the XACML spec... typical XML-base spec... table of contents enumerates the syntactic elements. semantics isn't visible from TOC
ah... semantics is found in section 7. Functional requirements
Shortly after I started at Microsoft, I had the opportunity to meet with the people behind Exchange, Outlook, MSN, Windows Mobile, Messenger, Communicator, and more. We brainstormed about this “meshed world” and how we might best serve it - a world where each of these products and others’ products could both manage these objects and synchronize each others’ changes.
-- Ray Ozzie
The model behind SSE is pretty straightforward; to sychronize data across multiple sources, each end point provides a feed and the subscribes to the feeds provided by the other end point(s).
Seems a lot like the Peer-peer update and sync section of the RDF Delta paper.
The drupal theme we're using is XHTML-happy, but doesn't know that it's rude to change the font size of body text. Anybody wanna clue me in on how to fix it? update: seems somebody fixed it. I wonder how. It seems like all the fonts got bigger, not just the main body text.
I've been playing around with the drupal taxonomy module. Why doesn't XML2005 show up under conferences?
I found the SIOC schema... it seems to create aliases for several widely-known terms. Ugh. I wonder why. update... the SIOC folks are aware of this and are discussing the relationship with foaf and skos. And it uses multiple domains as if the meaning was the disjunction, despite resolution of the issue of What should the semantics of multiple domain and range properties be?
My talk was:
@ 2:45 on Weds
Semantic Web Calendaring: RDF Calendar, hCalendar,
I spent a lot of time preparing my slides, Semantic Web Data Integration with hCalendar and GRDDL, but at show-time, there were still too many. I had to basically skip over the cool OWL DL consistency checking example that I spent the better part of two days putting together, but I'm OK with that; the more basic points were more important.
I unfortunately didn't leave any time for questions, but I had some interesting follow-up conversations:
- Somebody asked about using GRDDL and RDF to track relationships between specs, products that support them, and all that. I recalled that when the folks that run the OASIS standards registry contacted W3C, we told them we prefer a more decentralized approach: each organization publishes stuff about their own standards, in RDF, and anybody can aggregate it. TimBL's roadmap diagrams show one approach. It is somewhat bit-rotten, but we have an automated system in production for publishing basic title/author/date/version metadata about our specs and we're adding more stuff over time; e.g. which WG produced the spec (for patent policy reasons), comment due dates, etc. I told him this had come up in spec-prod; while I'm happy for the discussion to go there, my impression that it had come up there before was wrong. I hope to organize my thoughts on this near NormativeReferences in the QA/ESW wiki and re-kindle discussion in spec-prod or qa-ig.
- At lunch, somebody brought up my slide about email headers in RDF and asked if thunderbird has RDF support like mozilla and firefox. I don't know, but I hope to find out. DanBri? Anyone?
On the non-technical front, jamming with Len Bullard was a blast. We had a fascinating discussion of DRM and the recording industry where I relayed AaronSw's viewpoint that any model based on scarcity is uninteresting. Len says Prince is no longer independent, which contradicts the impression I got from studying Prince in Wikipedia recently. Len says the big customer ripie for SemWeb technology is transit, at least as much as intelligence. Gotta look into that.
Later in the evening Len brought out a fake book and Tony and Lauren and Eve and John sang and I tried to accompany them on Len's guitar. I was having so much fun that I raised a sizeable blood-blister on my strumming hand before I noticed. I think we did OK with Annie's Song as well as mangling lots of Beatles and such.
Then Len took the guitar and Eve asked him to play Angel from Montgomery by Bonnie Raitt. When he said he didn't know it, I was able to use my sidekick to find chords and lyrics and since it was your basic three chord number, he picked it up in no time.
As to the conference program...
Tue 15 Nov
Keynote: From Atoms to OWLs the new ecology of the Semantic
Jonathan Robie said Jim made 5 or 6 points in this talk that had been obscure, at best, in earlier talks on the Semantic Web in RDF. Kurt Cagle's notes don't seem to show them.
Unfortunately, the DAWG teleconference started at 9:30 and missing it would have delayed the WG by several weeks, so I ducked out.
Math in Real-World Workflows: Practical Lessons
What jumped out at me was that primary school publishers are hot on MathML content markup for reasons of accessibility. It's good to hear that the theory that higher levels of semantic abstraction contribute to accessability plays out in practice.
I asked if XSL-FO was on the map in this world of production math workflows, but he said no, not really.
I wanted to ask
what would you change about mathml if you had a time machine?but didn't find the right moment.
@14:00.Modeling Methods and Artifacts for Crossing the
He had this great slide (5 of 37) showing that business data goes from narrative documents (catalogs) to transaction data (orders) and back to narrative (support docs) and that data models need to cross them.
An HL7 person asked
how important is it to trace back from document to data model?which prompted me to add a slide to my talk to make the point about how GRDDL lets you get from narrative documents back to UML-like models.
*14:00.Federated Identity Management: An Overview of
Concepts and Standards
I really wanted to get this overview from Eve, but I got caught in a hallway conversation or something and missed it. I picked up some of how Liberty works from the next talk. ID-FF looks an awful lot like OpenID. I wonder what's the difference.
@14:45.Liberty Federation Deployment Case Study
This showed real-world deployment of federated identity services remarkably like the ones we discuss in the PAW project. I asked a lot of questions about the details, and the answers were quite reasonable. Afterward, I said to Eve and Yvonne,
Would you slow down? We're trying to pitch many of these ideas to research funders. If you deploy them all in commercial settings, where will we be? ;-)
At some point, she mentioned government rules where authorization data was considered sensitive but authentication data was not. I hope to get more details about that.
*14:45.Microsoft's Language Integrated Query and XML
I heard this was a great talk; both the content and the presentation. I hope to get notes from Norm, Michael, and others who were there.
@16:00.The Atom Publishing Protocol: Publishing Web
Content with XML and HTTP
Most of the stuff he presented looked familiar; looks like not much has changed since the last time I saw Joe give a talk on the Atom protocol. He mentioned
great article by Udell on URIs... ah... Tangled in the threads seems to be a column that Udell used to write for Byte. Anybody got a pointer to the article Joe was talking about? I'd like to cite it among the TAG educational materials.
- @16:45.Remixing RSS - past, present and future
.Names, Namespaces, XML Languages and XML Definition
I think Henry alluded to this paper in a TAG discussion of XMLVersioning-41 in Edinburgh. I was looking forward to getting it presented conference-style, but I guess I can read the paper and discuss it in the TAG.
Wed 16 Nov
11:45 . On Language Creation
missed this in the panic of preparing for my talk. Darn.
11:45 . Native XML Scripting with ECMAScript for XML
missed this in the panic of preparing for my talk. Darn.
- @ 14:00 . XSL Transform Self-Documentation
16:00 . XML, REST, and SOAP at Yahoo
Wanted to follow up on the conversation we started briefly in his blog but it was scheduled against a SPARQL session. Had to settle for a brief hand-shake and card exchange.
16:00 . SQL, XQuery, and SPARQL: What's wrong with this
What looked like a SPARQL-bashing session turned into a pretty good SPARQL tutorial. Jim Melton, who has been doing SQL standards work for over 20 years and sharing that experience in the XQuery WG for several years, took a close look at SPARQL, prompted by some nifty results by some folks using RDF/OWL in drug discovery. Even though he was "strongly encouraged" to conclude that SPARQL was obviated by SQL and XQuery, his conclusion was that it has a place.
Thu 17 Nov
09:00 . Describing Web Applications
missed the talk but spent some time noodling on WebDescriptionProposals in the ESW wiki. I hope to study WADL more closely.
- * 09:00 . Semantics and Security: Applying RDF and OWL to Defense and Security Challenges
11:00 . The Impact of XML on Contract Law and the Volume of
I didn't get to see Jane Winn's talk (though it won an award and I look forward to reading the paper), but after Bob G. introduce me to her in the exhibit hall, we had a fascinating discussion of the social side of open source and open standards. There's some seminal paper on charismaric leadership that she's supposed to be sending me. I asked for a pointer, but it seems to come from the pre-Web world of paper and fax machines.
11:00 . Unit Testing in XSLT 2.0
Some comments on XSLT 1.0 were pushed back a la
but wer're just doing a transformation language for stylesheets, not a general-purpose programming language.Maybe so, but clearly XSLT 2.0 is sufficiently general purpose to build unit testing harnesses.
11:45 . Automated mass production of XSLT stylesheets
Using a spreadsheet as a way to communicate design requirements and even decisions from users to developers and/or straight to the machine. Cute. Reminds me of my own work on using spreadsheets as an RDF authoring tool.
- * 14:00 . "Just" Use XML
14:45 . A Generalized Grammar for Three-way XML
This was much less relevant to our work on RDF diff/sync than I thought it might be, but trick of using SVG animation to show differences between images was really cool.
16:00 . Using XSL, XForms and UBL together to create
complex forms with visual fidelity
I have missed so many chances to soak up XForms at a conference... I finally made the time for this one, but it turned out to me more about XSL-FO.
16:45 . Enterprise-level Web Form Applications with XForms
John Boyer is an XForms WG co-chair, as well as doing DSig stuff. He's now at IBM, since they acquired Pure Edge. Hendler got the two of us together in the hall to discuss some connection between XForms and SPARQL... something about using XForms in the role that XSLT plays in handling SPARQL results. Hmm.
John asked that we "don't think of a Form as just the typical name/address or pizza order form"; likewise, he asked us to put aside our notion of table. But I didn't get a firm feel for what we're supposed to put in thier places, except that a form can be a blackjack game.
20:00 . Closing Keynote: Everyone's using XML,
but does anyone care?
Very entertaining. On Web services, he said
we've got this little pea of xml under all these layers and only a true xml princess can feel it.
In the TAMI project, K is giving us clues about how the U.S. federal government works. She told us a bit about the federal register. It seems to be one of the main PaperTrails of the U.S. government; reminds me of an item about learning about the Hansard at XTech.
tags pending: TAMI? transparent datamining?
In a PAW project discussion of writing assignments for WWW2006, KR, etc., I asked that we use XHTML rather than LaTeX to collaborate on the papers.
The WWW2006 deadline is too soon to make the transition, but I took the source of one of the papers in development and translated it to XHTML in order to test my Transforming XHTML to LaTeX and BibTeX tools. Since the tools have only been tested on one project, of course they needed some tweaks. And they'll need some more for figures.
But I'm hopeful that it'll be cost-effective to do things this way.
Meanwhile, there's a cite-formats discussion in the microformat community. My work includes a microformat for bibliography stuff. I haven't figured out URIs for the properties nor converted it to RDF just yet, like I did for my old index of URI schemes and like we did for automating publication of W3C tech reports.
I recently took a turn leading discussion in the Notions & Notations class; I presented Issues in Semantic Web Logic, a hasty set of slides based on one of TimBL's DesignIssues notes, The Semantic Web as a language of logic. I expected that the idea of dropping the law of excluded middle in order to deal with self-reference paradoxes (liar's paradox, Russel's paradox, ...) would be controversial. It wasn't at all, to this audience. Hmm... See also: LogicalReflection wiki topic.