As I see it, SM3 v. 2.901 needs the secext import in Security.xsd, as that latter schema is referring to some objects that are supposed to be defined in the wsse namespace, which is only resolved in the secext schema.
So I'm sure somebody activated that import consciously, perhaps not resolving all the implications in other schemas (or not sharing all changes in their local sandbox).
Anyhow, things should be fine, if we can get approval for the proposed changes of yesterday or get corresponding proposals. That may likely have to be done by the IDS group.
Daniel is already in contact with them. I assume we're close to resolving these issues.
Norbert
-----Original Message-----
From: sm3-bounces at pwg.org [mailto:sm3-bounces at pwg.org] On Behalf Of Zehler, Peter
Sent: Tuesday, July 08, 2014 8:01 AM
To: Semantic Model 3.0 Workgroup discussion list
Subject: Re: [SM3] SM3, version 2.901: latest changes by NS
I checked the last version I published and secext.xsd was commented out. I agree with Norbert that the problems are just oversights. Someone should review the changes in detail. I gave them a once over and they look alright to me. It would be better to have someone actively involved to take a look as well.
Peter Zehler
Email: Peter.Zehler at Xerox.com
Office: +1 (585) 265-8755
Mobile: +1 (585) 329-9508
FAX: +1 (585) 265-7441
US Mail: Peter Zehler
Palo Alto Research Center Incorporated
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
-----Original Message-----
From: sm3-bounces at pwg.org [mailto:sm3-bounces at pwg.org] On Behalf Of Norbert Schade
Sent: Monday, July 07, 2014 3:55 PM
To: Semantic Model 3.0 Workgroup discussion list
Subject: [SM3] SM3, version 2.901: latest changes by NS
I've modified 2 files only:
- Security.xsd
o Right at the top of the schema we import 4 other schemas. The fourth one (xxx_secext_1.0.xsd) referenced a http schemaLocation. I changed that to a relative location (removed the folders prefix).
o Changed ClientRoleWKV to ClientTypeWKV
- ServicesOperations.xsd
changed a few objects with the 'SecurityAttributes' snippet in them to a 'SecurityElements' snippets.
All schemas validate with my XMLSpy after these changes.
I'm quite sure that the issues were oversights. So if somebody who worked on the critical objects could confirm that the changes are appropriate respectively improve the changes, we could finalize the current version.
I placed the NSValidationChanges-v2.901-20140707 zip file that contains these 2 schema files in the sm3/white folder on the pwg ftp site.
Regards
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.orghttps://www.pwg.org/mailman/listinfo/sm3
_______________________________________________
sm3 mailing list
sm3 at pwg.orghttps://www.pwg.org/mailman/listinfo/sm3