Hi Norbert,
By PWG process rules, we don't ever delete files from the PWG
FTP/HTTP server - that is, all URI in emails are durable.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto: blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
On Thu, Jul 10, 2014 at 12:46 PM, Norbert Schade <
Norbert.Schade at conexant.com> wrote:
> I'm just doing fine with Joe's 4 schemas on top of v. 2.901.
> Everything validates nicely.
>> I'm pretty much expecting another formal SM3 release any minute now.
> After that I will remove my zip file from sm3\white.
> Norbert
>> -----Original Message-----
> From: sm3-bounces at pwg.org [mailto:sm3-bounces at pwg.org] On Behalf Of
> Murdock, Joe
> Sent: Wednesday, July 09, 2014 7:05 PM
> To: sm3 at pwg.org> Subject: Re: [SM3] SM3, version 2.901: latest changes by NS
>> Sorry for the delay in responding. I was away in vacation.
>> I've posted updated schema and WSDL files at:
>ftp://ftp.pwg.org/pub/pwg/sm3/white/ids-changes-v2.901-20140709.zip>> The following changes were made:
>> PwgSystemControl.xsd and ServiceOperations.xsd = change from
> SecurityAttributes to SecurityElements per previous IDS review
>> PwgWellKnownValues - change ClientTypeWKV to ClientRoleWKV per IDS review
>> security.xsd - retained Norbert's change to use local copy of
> oasis-200401-wss-wssecurity-secext-1.0.xsd.
>> Joe
>> -----Original Message-----
> From: sm3-bounces at pwg.org [mailto:sm3-bounces at pwg.org] On Behalf Of
> Norbert Schade
> Sent: Tuesday, July 08, 2014 5:33 AM
> To: Semantic Model 3.0 Workgroup discussion list
> Subject: Re: [SM3] SM3, version 2.901: latest changes by NS
>> 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.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> _______________________________________________
> 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>