Re: [License-discuss] Request for feedback: public specification licensing

2024-07-17 Thread Bruce Perens via License-discuss
On Tue, Jul 16, 2024 at 8:37 AM Giacomo Catenazzi wrote: > But a standard is much more then just API and structures. As we learned: > "nobody can build a network stack just reading RFC, without looking BSD > code", for this reason "reference implementation" is important (and part > of the origina

Re: [License-discuss] Request for feedback: public specification licensing

2024-07-17 Thread Rob Landley
On 7/16/24 11:38, Simon Phipps wrote: > Hi! > > On Tue, Jul 16, 2024 at 5:09 PM Roland Turner wrote: > > It's not a revenue question. The important issue is that all copies of > an interoperability standard must say the same thing, or > interoperability itself is defeated. > > Having

Re: [License-discuss] Request for feedback: public specification licensing

2024-07-17 Thread Rob Landley
On 7/16/24 10:35, Giacomo Catenazzi wrote: > On 15.07.2024 18:43, Bruce Perens via License-discuss wrote: > >> In particular, you can't copyright function call signatures, variable >> names, return values, data structures, pretty much anything a software >> standard would cover. Oracle tried. We