WS Description WG Issues List

Comments on this list should be sent to the www-ws-desc@w3.org mailing list (Archives).

Summary List of Outstanding Issues

id	Status	Spec	Topic	Class	Req	Title
290	Active	Discussion of Alternative Schema Languages		Editorial		Typo in http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817/
289	Active	RDF Mapping		Design		URIs where we should provide RDF representation

id	Spec	Class	Status	Raised By
289	RDF Mapping	Design	Active	Jacek
	Title: URIs where we should provide RDF representation
	Description: [email] [Search or Google WG archive for relevant posts.]
	Proposal:
	Resolution:
290	Discussion of Alternative Schema Languages	Editorial	Active	Elliotte Rusty Harold
	Title: Typo in http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817/
	Description: [email]: In the very first sentence, "This document captures the result of discussions by the Web Services Description Working Group regarding WSDL 2.0 type system extensibilty at the time of its publication." should be "This document captures the result of discussions by the Web Services Description Working Group regarding WSDL 2.0 type system extensibility at the time of its publication." That is, extensibility is misspelled. [Search or Google WG archive for relevant posts.]
	Proposal:
	Resolution:

id: Issue number
Title: Short title/name of the issue
Spec: Document referred to in issue (AM = Abstract Model, Spec = WSDL Specification
Description: Short description of issue, possibly including link to origin of issue
Req: Link to WS Description Requirement that motivated this issue
Topic: Rough topic categorisation, one of: env(elope), rpc, enc(oding), meta(issue), bind(ing), fault
Class: Design or Editorial
Status: One of: Unassigned, Active, Closed, Postponed
Proposal: Current proposal for resolution of issue, possibly including link to further text
Resolution: Short description of resolution, possibly including link to a more elaborate description
Raised by: Person who raised the issue
Owner: WS Definition WG Member responsible for the issue

Maintained by Jonathan Marsh.