public-ws-resource-access-notifications@w3.org from July 2009 by subject

[Bug 6392] Transfer-GetResponse violates WS-I BP

[Bug 6401] Eventing: Notifications violates WS-I BP

[Bug 6411] MEX: no way to create metadata

[Bug 6413] Transfer- Move Fragment support from RT to Transfer

[Bug 6421] Eventing: Extension point in reply message of Unsubscribe

[Bug 6432] Eventing: Push delivery mode does not work when the subscriber is not addressable

[Bug 6500] MEX: Wrappers around GetMetadata

[Bug 6551] Transfer - Message processing time exceeded

[Bug 6680] MEX Section 3.2 has inconsistent properties

[Bug 6692] WS-Eventing: Remove Mode from the specification

[Bug 6699] RT: ability to assign metadata during create

[Bug 6711] Transfer - Defining what type of resource I am creating

[Bug 6719] MEX: What does the MEX dialect denote?

[Bug 6720] Transfer: Metadata returned by WS-Transfer GET unclear

[Bug 6724] Eventing: define resource representation

[Bug 6803] RT: Is this functionality required?

[Bug 6917] WS-Eventing: Performance Flaw

[Bug 6975] WS-Transfer needs to define the term 'literal resource representation'

[Bug 6980] Eventing: which came first - the filter or the format?

[Bug 7014] Transfer: Define a "Resource Representation" ContentDescription URI

[Bug 7039] Eventing: wse:Identifier is asking for trouble

[Bug 7068] Transfer: what's the schema of the resource

[Bug 7088] New: Transfer: Define the ws-fragment spec

[Bug 7088] Transfer: Define the ws-fragment spec

[Bug 7122] MEX: clarity around @Content

[Bug 7122] New: MEX: clarity around @Content

[Bug 7127] Can event information contained in notification be bound to soap:headers

[Bug 7127] Eventing: Can event information contained in notification be bound to soap:headers

[Bug 7127] New: Can event information contained in notification be bound to soap:headers

[Bug 7136] New: Suggested edits/cleanup of wrapped/unwrapped defintions.

[Bug 7159] ALL: WS-Eventing lies about sending faults

[Bug 7159] New: WS-Eventing lies about sending faults

[Bug 7160] Eventing:should not use should or may

[Bug 7160] New: Eventing:should not use should or may

WWW/2002/ws/ra/edcopies entitieswd.dtd,1.9,1.10

WWW/2002/ws/ra/edcopies specit,1.1,1.2

WWW/2002/ws/ra/edcopies wseventing.html,1.60,1.61 wst.xml,1.40,1.41

WWW/2002/ws/ra/edcopies wseventing.html,1.61,1.62 wseventing.xml,1.52,1.53

WWW/2002/ws/ra/edcopies wseventing.html,1.62,1.63 wseventing.xml,1.53,1.54

WWW/2002/ws/ra/edcopies wseventing.html,1.63,1.64 wseventing.xml,1.54,1.55

WWW/2002/ws/ra/edcopies wseventing.html,1.64,1.65 wseventing.xml,1.55,1.56

WWW/2002/ws/ra/edcopies wseventing.html,1.65,1.66 wseventing.xml,1.56,1.57

WWW/2002/ws/ra/edcopies wsmex.html,1.42,1.43 wsmex.xml,1.31,1.32

WWW/2002/ws/ra/edcopies wsmex.html,1.43,1.44 wsmex.xml,1.32,1.33

WWW/2002/ws/ra/edcopies wsrt.html,1.37,1.38 wsrt.xml,1.26,1.27 wst.html,1.44,1.45

WWW/2002/ws/ra/edcopies wst.html,1.45,1.46 wst.xml,1.41,1.42

WWW/2002/ws/ra/edcopies/ws-evt eventing.xsd,1.12,1.13

WWW/2002/ws/ra/edcopies/ws-mex MetadataExchange.xsd,1.4,1.5 metadataexchange.wsdl,1.2,1.3

WWW/2002/ws/ra/edcopies/ws-rst wsrt.xsd,1.3,1.4

WWW/2002/ws/ra/edcopies/ws-tra transfer.xsd,1.5,1.6

Last message date: Friday, 31 July 2009 21:39:12 UTC