XML Security Working Group Members Page (original) (raw)

XML Security WG Members-Only Administrative Page

This is the XML Security WG's Administrative page. All technical matters, unless they are Member-confidential, must be conducted in public as per the Working Group charter.

My Actions |My Questionnaires | WG Publication |Upcoming Meetings |Scribe Instructions | Implementations | Interop |Completed Meetings | Liaisons | LC Comment Tracker

General information:
IRC |Mailing Lists |Wiki |Process | Roadmap |Teleconferences |Presentations |W3C Events |Scribing |Action and Issues Tracking |Actions |Issues |Contact Info |Public Page | PAG

Meetings

Upcoming Meetings

Information about upcoming meetings is now on the public minutes page.

Completed Meetings with Draft Minutes for review

Information about completed meetings is now on the public minutes page.

Liaisons and Coordination

Coordination within the W3C:

XML Coordination Group

Chair of XML Security participates in regularly scheduled eleconferences. Group includes representatives from EXI, Service Modelling, XML Core, XML Processing, XML Query, XML Schema, XSL, XML Security.

The Forms Working Group (XForms)

Planning joint session at TPAC 2008 to discuss requirements.

Efficient XML Interchange (EXI) Working Group

Held joint session during XML Security Specifications Maintenance WG. (minutes, EXI Overview slides and EXI joint-meeting slides).
Planning joint session at TPAC 2008.

XML Core

No current plans.

XML Schema

No current plans.

XSL Working Group

Joint discussion on 16 September 2008.

Web Applications Working Group (WebApps)

Joint session planned for TPAC 2008.

Web Services Policy Working Group (WS-Policy)

Proposed changesto reference XML Signature (Second Edition) and Canonical XML 1.1 and to correct text related to suitability of XML Signature and Canonicalization when using xml:id.Errata E01 for WS-Policy Framework Recommendation and Errata E01 for WS-Policy Primer Note accepted and published.

Coordination external to W3C:

OASIS Security Services (SAML) TC

A few members of XML Security WG are also members of SSTC. Frederick raised issue at SSTC of updating references to XML Signature (Second Edition).

OASIS Web Services Secure Exchange (WS-SX) TC

A few members of XML Security WG are also members of WS-SX. Frederick raised issue of updating references to XML Signature (Second Edition), also noted possible issue with C14N10 algorithm URI.

OASIS Web Services Federation (WSFED) TC

Bruce Rich raised issue of updating references to XML Signature (Second Edition).

Java Community Process

• JSR 105, XML Digital Signature APIs
• JSR 106, XML Digital Encryption APIs

There is some overlap of membership.

Scribing

Minutes of each meeting are recorded by the scribe, using IRC. This is a task that will be shared by working group members on a rotating basis. The chair will not scribe. Please review the scribe instructions.

W3C Events

Upcoming W3C Events

Phone - Working Group Teleconferences

Our weekly teleconferences will be held 10-12 am Eastern on a weekly basis.

Warning on 27 October: Daylight Saving Time ends in Europe one week earlier than in US, so effectively call is hour earlier in Europe than usual: 14:00 - 16:00 London ; 15:00 -17:00 Paris, just for this one meeting.

• See time in your time zone.
• W3C Calendar entry

We will use the Zakim Bridge - see the Zakim Bridge instructions, and the list of phone numbers for Zakim. The Boston area number is +1.617.761.6200. The conference code is 965732 ("XMLSEC").

Please mute when you are not speaking, To mute while on Zakim dial 61#; to unmute, dial 60#.

IRC

Working Group participants are invited to join the W3C IRC server. The server is irc.w3.org, port 6665, and the channel for the XML Security is #xmlsec.

Member participants can also use the Web IRC interface which is useful when having firewall issues.

For information about IRC, please see the W3C IRC documentation, the Zakim agent's documentation, and the RRSAgent documentation.

Action and Issues Tracking

WG issues and actions should be associated with WG products ( text list ). The WG will use an XMLSec Tracker instance - general information on Tracker is also available at the Tracker home page.

Actions

WG Actions are recorded using Tracker.

• My Tracker
• List of All actions, Open, Pending, Closed ( text list )
• List of Open actions ( text list )
• List of Pending actions ( text list ), completed actions pending WG review before being closed.
• XMLSec Tracker page
• Information at Tracker Home Page

Closing Actions

Once you complete an action, please do the following:

1. Send an email to the public-xmlsec mailing list (unless the action resolution is member confidential) stating the details of the resolution of the action and noting that it should be closed. In the body of the message refer to "ACTION-#" - this will cause a link to the email to be automatically associated with the action record.
   Please use email "Subject: summary-of-item - ACTION-# completed" where the summary-of-item is some text to describe what was done.
2. Change the state of the action to "pending" using tracker. Pending means that the action is completed according to the owner and is ready for the WG to approve closing the action. The item should only be closed once agreed during a WG call. (You can change the status by going to My Tracker, clicking on the action, and choosing to "Edit this Action", changing the State to pending, and selecting "Update").

To close actions on IRC, type:

ACTION-NNN closed

Issues

Issue Tracking

Issues are recorded using the Tracker.

Raising Issues

Issues may be entered directly in tracker - this should result in an email being sent to the mailing list. This is the preferred approach of raising an issue. Alternatively, an issue may be raised by email, with the Subject line containing the text "NEW ISSUE: title"at the start, where title is the short descriptive name as outlined below. Please try to use tracker to raise issues.

General information for New Issues

Please provide the following information in a new issue (note this was suggested from the practice in the WS-Policy WG):

• Title - A short descriptive name for the issue
• Description - A longer and complete description of the issue, state in terms of the documents
• Justification - Why is this an issue? E.g., state an architectural concern, demonstrate an interop problem, explain a use case that isn't met
• Target - What deliverable the issue is against.
• Proposal - A reasonably complete proposal for how the issue should be addressed.

It is also appreciated if the proposed solution comes with test cases.

When creating an action, please make sure it is entered in tracker and associated with a product in tracker, as well as sending an email.

• List of Issues ( text list )
• List of Raised issues ( text list )
• List of Open issues( text list )
• Requirements tracker

WG Questionnaires

Open WG questionnaires.

Mailing Lists

The WG uses the member-xmlsec mail list for administrative and Member-private e-mail (see the archive).

The public mail list public-xmlsec should be used for XML Security technical discussions (see the archive).

Process

W3C 101 Introduction

Should have working draft for every deliverable, should publish early and often, have working draft every three months.

Draft Roadmap

Presentations

1. XForms Signature presentation (PDF), (ODP)
2. NVDL and XML Signature (PDF), (PPT)

Chair: Frederick Hirsch
Team Contact and Security Activity Lead: Thomas Roessler
Id:Overview.html,v1.4632016/10/1112:26:48domExpId: Overview.html,v 1.463 2016/10/11 12:26:48 dom Exp Id:Overview.html,v1.4632016/10/1112:26:48domExp

Copyright© 2006-2008 W3C® (MIT, ERCIM,Keio), All Rights Reserved. W3C liability,trademark,document use and software licensing rules apply. Your interactions with this site are in accordance with our publicand Memberprivacy statements.