A quick update: Confirmation on time/dates of the latest schema text files will be forthcoming after the July 6 meeting I mentioned below. Sorry I won't be able to confirm before that. Thanks again for your patience...
From: Bill Wesse Sent: Wednesday, June 30, 2010 7:57 AM To: '[email protected]' Cc: MSSolve Case Email Subject: [REG:110062452298172] Text-file Schema for all of 2000-2008R2 Hi Andrew. I am advised that a planning meeting including the topic of where we intend to post the schema text files is scheduled for next Tuesday (July 6). I will advise you on the results as soon as I can after that (it is occurring very late in the day, my time). ... Regards, Bill Wesse MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC Protocol Team 8055 Microsoft Way Charlotte, NC 28273 Email: [email protected] Tel: +1(980) 776-8200 Cell: +1(704) 661-5438 Fax: +1(704) 665-9606 -----Original Message----- From: Bill Wesse Sent: Thursday, July 01, 2010 1:19 PM To: "Andrew Bartlett" <[email protected]> Cc: "MSSolve Case Email" <[email protected]>; "[email protected]" <[email protected]> Subject: [REG:110062452298172] Re: Text-file Schema for all of 2000-2008R2 Hello again Andrew; Schema text file zip attached... My confidence that the files are the latest is ~8 on a scale of 1-10. I won't know more until later today, more likely tomorrow. Concerning the support limits - I think they are 'provided as-is', per #Tools below; confirmation pending from same people who will verify latest/not-latest. Concerning the errors in earlier file sets, I also find it hard to understand why there are any at all - unless they were generated using an imperfect utility (the most likely reason). But I simply don't know. From the files: #Intellectual Property Rights Notice for Protocol Documentation ... #Tools. This protocol documentation is intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. A protocol specification does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Regards, Bill Wesse MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC Protocol Team 8055 Microsoft Way Charlotte, NC 28273 Email: [email protected] Tel: +1(980) 776-8200 Cell: +1(704) 661-5438 Fax: +1(704) 665-9606 -----Original Message----- From: Bill Wesse Sent: Wednesday, June 30, 2010 10:10 AM To: "Bill Wesse" <[email protected]> Cc: "MSSolve Case Email" <[email protected]>; "[email protected]" <[email protected]> Subject: [REG:110062452298172] Re: Text-file Schema for all of 2000-2008R2 On Wed, 2010-06-30 at 11:57 +0000, Bill Wesse wrote: > Hi Andrew. I am advised that a planning meeting including the topic of > where we intend to post the schema text files is scheduled for next > Tuesday (July 6). I will advise you on the results as soon as I can > after that (it is occurring very late in the day, my time). OK. Please just post them in a reply to cifs-protocol in the meantime. > Meanwhile, I am currently waiting for confirmation on the latest file > dates for the schema files we have provided. I expect to have that > info within the next day or so. OK. Can you give me some indication as to your level of confidence that the latest files match what is actually found in the respective AD versions? I just want to set my expectations correctly before I start trying to have Samba load them. > Also, there are some limits on our support level for the schema text > files – I will also advise you on that (query in progress…). I'm sorry to hear about the limitations on the support for the schema files. We only ask for them because we found the PDF documents to be both inaccurate and unusable for the purpose for which they purport to be provided (the creation of interoperable implementations). We do appreciate the extra effort that has gone into providing them, and getting them under an acceptable licence, but it is only by the provision of text-format schema that we have been able to show how deficient the documentation has been in the first place. I still don't understand how so many errors crept into a document that should be no more than a reformat of a direct extract from the version control system for the relevant AD versions. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Cisco Inc. _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
