[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [provision-comment] Public Comment
Nir, There are several proposals currently under consideration for adding complex data support to SPML. I will be glad to explain how this would be supported in the OpenNetwork Technologies proposal. In the ONT proposal, complex data can be passed as the contents of the value element and the SPML Schema that defines that element would reference an XSD which defines the allowed syntax of the XML. Thus a client can make an smpl:schemaRequest to retrieve the SPML Schema for a service, and then that schema could then be used to validate the fields like you want to do. The ONT proposal also has a mechanism to pass the provisioning data only as XML, with out relying on attribute value pairs. Using this mechanism, XSD is included in the SPML Schema that defines the allowed syntax of the XML. The choice of which mechanism to use would be left to the SPML service implementer. Of course the committee is still considering several proposals for this so it's too early to say how this will all work out in the end. Jeff Bohren Product Architect OpenNetwork Technologies, Inc Try the industry's only 100% .NET-enabled identity management software. Download your free copy of Universal IdP Standard Edition today. Go to www.opennetwork.com/eval. -----Original Message----- From: comment-form@oasis-open.org [mailto:comment-form@oasis-open.org] Sent: Thursday, January 22, 2004 8:57 AM To: provision-comment@lists.oasis-open.org Subject: [provision-comment] Public Comment Comment from: nir_z@hotmail.co.il Hi Two years ago when we designed our provisioning system it was obvious we will use XML to send provisioning requests. When we designed our XML our guidelines were performance and maintainability. Regarding maintainability - we wanted that all field validation will be done using XSD, thus minimizing code changes. We ended up with XML where each field/attribute is defined as a node in the XML and the XSD define each specific field content (using types, enumerations, patterns, etc). Now we're considering adopting the SPML where each field/attribute is identified by the attribute "name" of the node <attr>. Is there a way to validate the content of the <value> node according to the value of the "name" attribute in the <attr> node using XSD (or another standard method)? Thanks Nir Zayden To unsubscribe from this list, send a post to provision-comment-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]