W3C XML-Encryption FTF

Boston, MA
01 March 2000

See the W3C Plenary page for general and logistic information.

DRAFT PROGRAM

The goal of this meeting is to get closure on open issues, all of which I hope are captured in the requirements document. These issues are captured from the list and proposals. Please be very familiar with both of these documents. This then should then be reflected in a ASAP publication of a Requirements Working Draft (WD), and an subsequent specification WD.

I'm looking for folks to volunteer to present issues and maybe lead a brain-storming session. Volunteers for minutes are solicited: 3 note takers for 2 hour chunks.

THURSDAY 01 March

8.30 - 9.00 Continental Breakfast

9.00 - 10.00 (60 minutes): Introduction :)

Introduction, History, Charter (deliverables, scope, IPR). Joseph Reagle.

10.00 - 10.30 (40 minutes): Requirements - Easy Issues.

Quick review of some of the easier outstanding issues

Data Model/Vocabulary
1. Node - abstract item in DOM or XPath.
2. Element - Element Information Item: start/end tag, their attributes, and everything between.
3. Element Children - element, processing instruction, unexpanded entity reference, character and comment information items: everything between the start and end tags
4. Element Content - All the character children of an Element Information Item; the characters occuring between the start/end tag.
The processing model should be based on application specific logic, or XSLT, XPath, etc?
Objects and Encodings
1. When an external object is decrypted, it should return to its native MIME type.
2. How do we describe the type of the thing decrypted?
3. Do we do base64 and/or hex?
Referencing model: do we use URI and/or fragements, XPath, XPointer?
Integrity: do we specify simple encryption+integrity, or rely upon XML Signature?

10.30 - 10.45 break

10.45 - 11.45 (60 minutes): Latest Proposal

Overview of latest proposal

EncryptedData Structure, Ed Simon (25 minutes)
EncryptedKey Structure, Blair Dillaway, (25 minutes)

11.45 - 1.00 (75 minutes): Requirements - Difficult Issues

Introduction to difficult issues

Granularity: Attribute Encryption and Arbitrary External Data. Ed Simon
Signing and Encryption. Joseph Reagle and Hiroshi Maruyama
Transform feature (if any) and Algorithm support. ?Volunteer?
Syntax (namespaces, structures, and open issues in proposal). ?Joseph Reagle?

1.00 - 2.00 lunch (60 minutes)

2.00 - 3.00 Refocus on Difficult Issues (90 minutes)

Conversation

3.00 - 4.00 Break Out

Form subgroups for discussion and creation of proposal if necessary.

4.00 - 5.00 Close Issues

Identify what has been agreed to, and propose methods of closing others (someone document alternatives, makes new proposal, discussed in teleconference, go with X and ask for wider review, etc.) Requirements Document

5.00 - 5.30 Logistics

When to have teleconferences, when to meet next?

Joseph Reagle <reagle@w3.org> Last updated: 19th September 2000.