[cifs-protocol] Status: CAR - ldap display specifiers (SRX090713600122)

[Bill Wesse]

I will be out of the office on vacation, returning Monday, September 7. My colleague, Hongwei Sun will be your contact during my absence.

Regards,
Bill Wesse
MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
TEL:  +1(980) 776-8200
CELL: +1(704) 661-5438
FAX:  +1(704) 665-9606


-----Original Message-----
From: Bill Wesse 
Sent: Tuesday, August 18, 2009 11:30 AM
To: 'tridge at samba.org'; 'Andrew Bartlett'
Cc: 'mdw at samba.org'; 'cifs-protocol at samba.org'
Subject: Status: [cifs-protocol] CAR - ldap display specifiers (SRX090713600122)

Good morning - and thanks for your patience. We are nearly complete with the property rights notice for the display specifiers ldf.

I expect to be able to make the final documents available to you within 3-5 working days!


Regards,
Bill Wesse
MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
TEL:  +1(980) 776-8200
CELL: +1(704) 661-5438
FAX:  +1(704) 665-9606


-----Original Message-----
From: Bill Wesse 
Sent: Monday, July 20, 2009 9:31 AM
To: 'Andrew Bartlett'
Cc: tridge at samba.org; mdw at samba.org; cifs-protocol at samba.org
Subject: RE: [cifs-protocol] CAR - ldap display specifiers

Good morning Andrew!

There is no copyright license for the attachments - yet; nevertheless, I expect the below text - or something like it - to apply. I cannot guarantee there will be no changes between now and when the CAR request is fulfilled. I certainly expect this will not take as long as it did with the schema.

Intellectual Property Rights Notice for Open Specifications Documentation

o Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. 

o Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. 

o No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. 

o Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp) or the Community Promise (available here: http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if the technologies described n the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting iplg at microsoft.com. 

o Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. 
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. 

o Tools. The Open Specifications do 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. Certain Open Specifications are 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. 


Regards,
Bill Wesse
MCSE, MCTS / Senior Escalation Engineer, US-CSS DSC PROTOCOL TEAM
8055 Microsoft Way
Charlotte, NC 28273
TEL:  +1(980) 776-8200
CELL: +1(704) 661-5438
FAX:  +1(704) 665-9606

-----Original Message-----
From: Andrew Bartlett [mailto:abartlet at samba.org] 
Sent: Monday, July 20, 2009 7:15 AM
To: Bill Wesse
Cc: tridge at samba.org; mdw at samba.org; cifs-protocol at samba.org
Subject: Re: [cifs-protocol] CAR - ldap display specifiers

On Mon, 2009-07-20 at 18:15 +1000, Andrew Bartlett wrote:
> On Fri, 2009-07-17 at 07:38 -0700, Bill Wesse wrote:
> > Tridge - every out of band release has a unique Intellectual 
> > Property notice. So the notice that was included in the schema is 
> > unique, and pertains only to the schema release that we provided (it 
> > can be obtained on the 'Microsoft Open Specification Support Team 
> > Blog' blog
> > at):
> > 
> > Using the Windows Server Protocols documentation set to better 
> > understand the Active Directory Schema 
> > http://blogs.msdn.com/openspecification/archive/2009/06/26/using-the
> > -windows-server-protocols-documentation-set-to-better-understand-the
> > -active-directory-schema.aspx
> > 
> > Once document development has detailed the precise nature of the final data we will be supplying, an IP notice will be attached!
> 
> I'm confused.  What is the copyright licence applicable to the 
> contents of the zip file you just mailed?

Also, if it is the licence you posted earlier in this thread, is this considered 'schema'?  (Given we need to incorporate the whole file, I need it to fall under the exception to the 'portions of' rule).

Thanks,

Andrew Bartlett
--
Andrew Bartlett
http://samba.org/~abartlet/
Authentication Developer, Samba Team           http://samba.org
Samba Developer, Cisco Inc.