[cifs-protocol] [REG:110062452298172] Re: Text-file Schema for all of 2000-2008R2
hongweis at microsoft.com
Tue Sep 7 18:36:22 MDT 2010
We have completed the process to use tools to automatically extract the Windows server 2008R2 schema from the schema documents and validate it against a Windows DC implementation. The schema file includes a EULA. Please review it and provide feedback. Although this is a private delivery, we are working to create a standard way to publicly publish the schema and we will provide further updates when we have finalized this plan.
From: cifs-protocol-bounces at cifs.org [mailto:cifs-protocol-bounces at cifs.org] On Behalf Of Andrew Bartlett
Sent: Tuesday, August 17, 2010 7:46 PM
To: Interoperability Documentation Help
Cc: MSSolve Case Email; cifs-protocol at samba.org; Bill Wesse
Subject: Re: [cifs-protocol] [REG:110062452298172] Re: Text-file Schema for all of 2000-2008R2
On Thu, 2010-07-08 at 11:43 +0000, Bill Wesse wrote:
> Resending the DumpSchema.cmd(.txt) file; I broke the earlier one during an edit (deleted a label ':Perform'). Sorry.
I was working on this with Bill, but I need to bump this a long a little, and to clarify things a bit more:
It is great having commands to dump the schema - we can write such commands easily, and use those to confirm that the schema we supply to our users is correct. Indeed, such commands have shown that we have not been supplied correct schema in the past.
However, what I need isn't tools to extract schema from AD servers, but the actual schema, provided by Microsoft to us under the agreed licence.
This makes it unambiguous that we can redistribute the result.
Therefore, we do require the schema from the WSPP documentation, we require it in a format that is suitable for use in creation of an interoperable implementation, we need is under the licence, and we require that it is 100% correct.
If we cannot get those assurances, we have two problems: We waste an inordinate amount of time fixing bugs that should never have occurred (surely the docs were generated with tools such as you supplied in your mail), and we loose confidence that any update to the schema or a new revision is correct.
Have you had any luck securing those assurances from the product group?
It seems to have taken quite some time, for something that should be nothing more than providing an automated extract.
Andrew Bartlett http://samba.org/~abartlet/
Authentication Developer, Samba Team http://samba.org
Samba Developer, Cisco Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 81575 bytes
More information about the cifs-protocol