[SM3] SM3, version 2.901: ClientRole

[SM3] SM3, version 2.901: ClientRole

[SM3] SM3, version 2.901: ClientRole

Norbert Schade Norbert.Schade at conexant.com
Fri Jun 27 18:51:34 UTC 2014


The PWGWellKnownValues schema has a ClientTypeWKV type, not a ClientRoleWKV type.
It's a simple type showing values like Proxy, User, Vendor.

Are we looking at some renaming issue here?
Norbert

-----Original Message-----
From: sm3-bounces at pwg.org [mailto:sm3-bounces at pwg.org] On Behalf Of Manchala, Daniel
Sent: Friday, June 27, 2014 2:45 PM
To: 'Semantic Model 3.0 Workgroup discussion list'
Subject: Re: [SM3] SM3, version 2.901: ClientRole

I believe the ClientTypeWKV (of which ClientRole belongs to) was earlier part of security.wsd and is now moved to PwgWellKnownValues.xsd. 

-----Original Message-----
From: sm3-bounces at pwg.org [mailto:sm3-bounces at pwg.org] On Behalf Of Norbert Schade
Sent: Friday, June 27, 2014 11:35 AM
To: Semantic Model 3.0 Workgroup discussion list
Subject: [SM3] SM3, version 2.901: ClientRole

The Security schema is simply the only file in that 2.901 zip that shows a ClientRole object resp. a type corresponding to it.
That explains the error.

Is there another schema somewhere else that has that type definition and probably was forgotten at some point?

Or has the ClientRole object become redundant by now?

regards
Norbert

-----Original Message-----
From: sm3-bounces at pwg.org [mailto:sm3-bounces at pwg.org] On Behalf Of Norbert Schade
Sent: Friday, June 27, 2014 2:29 PM
To: Semantic Model 3.0 Workgroup discussion list
Subject: [SM3] SM3, version 2.901: schema errors

I've downloaded PWG_SM_3.0_v2.901.zip and opened all schema files (xsd) in my XMLSpy, but not the WSDL files (I'm not an expert on that).

My current results with my XMLSpy:

-          ServiceOperations
that schema is not valid by itself.
therefore any schema that uses objects out of ServiceOperations.xsd crashes as well. Candidates for that are PWGSystemControlOpMsg.xsd, PWGSemanticModel.xsd and Serices.xsd.
it looks as if GetSecurityAttributesRequest and GetSecurityAttributesResponse are the critical objects in all cases.

-          xmldsig_core_schema
the schema is valid by itself.
however when used by ServicesOperations.xsd, the element 'Signature' of type 'ds:SifnatureType' causes trouble.

-          Security
that schema is not valid by itself.
element ClientRole of type ClientRoleWKV seems to be the problem.

No idea about the issues yet.
If somebody can make a useful comment before I run off into some unknown jungle, this is a good time to say it.
I'll look around a bit now.
Norbert

Norbert Schade
Systems Engineer (printing)
Imaging Solutions
Conexant Systems, Inc.
201 Jones Road
Waltham, MA 02451
U.S.A.
Tel: 1-781-370-8929
Email: norbert.schade at conexant.com<mailto:norbert.schade at conexant.com>

_______________________________________________
sm3 mailing list
sm3 at pwg.org
https://www.pwg.org/mailman/listinfo/sm3
_______________________________________________
sm3 mailing list
sm3 at pwg.org
https://www.pwg.org/mailman/listinfo/sm3
_______________________________________________
sm3 mailing list
sm3 at pwg.org
https://www.pwg.org/mailman/listinfo/sm3


More information about the sm3 mailing list