W3C home > Mailing lists > Public > xml-dist-app@w3.org > August 2001

proposed wording to address attributes

From: christopher ferris <chris.ferris@east.sun.com>
Date: Wed, 01 Aug 2001 16:57:10 -0400
Message-ID: <3B686D26.DD5AF866@east.Sun.COM>
To: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
All,

I took an AI to draft proposed wording to address handling of foriegn
namespace qualified attributes in response to Gudge's editor's note
in his Infoset draft [1] of the SOAP1.2 spec. To wit:

	"Ednote: I don't quite know what to do with respect to the 
	following paragraph. The exceptions for mustUnderstand and actor are
	almost incompatible with an Infoset approach. The rest of the paragraph 
	is redundant from an infoset perspective."

	"With the exception of the SOAP mustUnderstand attribute (see section 4.2.3) 
	and the SOAP actor attribute (see section 4.2.2), it is generally permissible 
	to have attributes and their values appear in XML instances or alternatively 
	in schemas, with equal effect. That is, declaration in a DTD or schema with a 
	default or fixed value is semantically equivalent to appearance in an instance."

As we discussed on the call [2] SOAP doesn't require schema processing.
Hence, attributes cannot be defaulted from the schema but must be carried
in the serialized SOAP envelope. The Infoset specification [3] defines a
property of an Attribute Information Item named [specified] that is:

	"A flag indicating whether this attribute was actually specified 
	in the start-tag of its element, or was defaulted from the DTD."

My proposed changes to Gudge's draft are captured in the attached 
revised draft.
	
Cheers,

Chris


[1] http://www.w3.org/2000/xp/Group/1/06/01/soap-02-infoset.html
[2] http://www.w3.org/2000/xp/Group/1/07/25-minutes
[3] http://www.w3.org/TR/xml-infoset/#infoitem.attribute

Received on Wednesday, 1 August 2001 16:57:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:03 GMT