Date   

Re: Spdx Digest, Vol 1, Issue 16

kate.stewart@...
 

Hi Jilayne,
Welcome. :)

--- On Mon, 8/30/10, Jilayne Lovejoy <Jlovejoy@...> wrote:

From: Jilayne Lovejoy <Jlovejoy@...>
Subject: RE: Spdx Digest, Vol 1, Issue 16
To: spdx@...
Date: Monday, August 30, 2010, 1:50 PM

1) I noticed the license list included some of the GPL
exceptions such
as Autoconf and Bison.  My understanding is that the
text for these
exceptions would be the exception itself (not the full
license) and so
there would need to be a way to pair the exception with the
proper GPL
version in such a way that is distinct from dual and
disjunctive
licensing situations.  Otherwise, we would need to
list each GPL version
with each exception as separate and whole licenses. 
Text for each exception, should include exception and original licenses.

2)  I noticed the license list included in the mailing
list is more
comprehensive than the one on the website - am I correct to
assume this
is only because the website has not been updated? 
Regardless, I'd be
happy to help sort through the BSD and MIT licenses once
the text is
available.
Web site is behind on being updated. What is most accurate right now is the spec document at http://www.spdx.org/spec/current. Its behind some of the proposals on the mail list. So if you could help sort out the BSD and MIT licenses that should be proposed to be added, it would be very much appreciated.


3) Regarding the BSD and Apache 1.1 licenses in particular
- both of
these incorporate the name of the author within the license
text.  This
is especially difficult in Apache 1.1 as it affects the
third, fourth,
and fifth clauses.  Where the license text is
otherwise verbatim, do we
have a way to handle this in terms of how the standard
license will
appear in the master list, as well as some sort of protocol
for how
"exact" a license must be to be matched to the standard
version?
To address this, we have been discussing the notion of a template version of the license, but haven't gotten around to figuring out the syntax of the parts that can vary and still comply. If you've got ideas here, feel free to propose to list, Daniel G. and Bob G. have been commenting on this as well.

4) Agree with Peter that the CeCILL licenses should be on
the list,
which then begs the question of how to deal with a license
that is
available in multiple languages (EUPL also comes to mind)?
re: EUPL... good question. Ideas are welcome. Probably need to treat each language version as separate version to be explicitly recognized.
Maybe suffix to determine language used? not sure... how common are the non-english licenses in practice?

Thanks, Kate


Re: Spdx Digest, Vol 1, Issue 16

Jilayne Lovejoy <Jlovejoy@...>
 

Hello,

I'm new to the mailing list so forgive me if any of my
questions/observations are redundant or minimally informed.
I had a couple thoughts regarding various posts and the license list
included in Issue 14.

1) I noticed the license list included some of the GPL exceptions such
as Autoconf and Bison. My understanding is that the text for these
exceptions would be the exception itself (not the full license) and so
there would need to be a way to pair the exception with the proper GPL
version in such a way that is distinct from dual and disjunctive
licensing situations. Otherwise, we would need to list each GPL version
with each exception as separate and whole licenses.

2) I noticed the license list included in the mailing list is more
comprehensive than the one on the website - am I correct to assume this
is only because the website has not been updated? Regardless, I'd be
happy to help sort through the BSD and MIT licenses once the text is
available.

3) Regarding the BSD and Apache 1.1 licenses in particular - both of
these incorporate the name of the author within the license text. This
is especially difficult in Apache 1.1 as it affects the third, fourth,
and fifth clauses. Where the license text is otherwise verbatim, do we
have a way to handle this in terms of how the standard license will
appear in the master list, as well as some sort of protocol for how
"exact" a license must be to be matched to the standard version?

4) Agree with Peter that the CeCILL licenses should be on the list,
which then begs the question of how to deal with a license that is
available in multiple languages (EUPL also comes to mind)?


Cheers,

Jilayne Lovejoy | Corporate Counsel
jlovejoy@...

720 240 4545 | phone
720 240 4556 | fax
1 888 OpenLogic | toll free
www.openlogic.com

OpenLogic, Inc.
Headquarters, Broomfield, Colorado 80021

-----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...]
On Behalf Of spdx-request@...
Sent: Monday, August 30, 2010 12:00 PM
To: spdx@...
Subject: Spdx Digest, Vol 1, Issue 16

Send Spdx mailing list submissions to
spdx@...

To subscribe or unsubscribe via the World Wide Web, visit
https://fossbazaar.org/mailman/listinfo/spdx
or, via email, send a message with subject or body 'help' to
spdx-request@...

You can reach the person managing the list at
spdx-owner@...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Spdx digest..."


Today's Topics:

1. RE: Names of licenses we currently support / where should
licensetext live? (Soeren_Rabenstein@...)
2. Some feedback I've received on the latest draft (Ciaran Farrell)
3. CeCILL licences (Patrick MOREAU)
4. Re: Names of licenses we currently support / where should
licensetext live? (Peter Williams)


----------------------------------------------------------------------

Message: 1
Date: Mon, 30 Aug 2010 10:07:49 +0800
From: <Soeren_Rabenstein@...>
Subject: RE: Names of licenses we currently support / where should
licensetext live?
To: <spdx@...>
Message-ID:
<BD0D39FA6F74634D856A51ADCC26F9452D95C7@...>
Content-Type: text/plain; charset="iso-8859-1"


Peter Williams wrote:
Once a license is "approved" and placed in the repo it should be
immutable. That way there is no chance of the text changing once the
license name is in use.
I agree.
Also: If an spdx document is supposed to contain all the license texts,
isn't there a danger that we end up documenting 10 KB of source code
with 1 MB of license texts? (Yes I know, if there one thing America
needs it's more license texts:
http://www.youtube.com/watch?v=0u9JAt6gFqM).

Imho the spdx list of standard licenses should cover as many licenses as
possible (whereas coverage of x % of the licenses in a common Linux
Distribution is not necessarily the standard of completeness, as spdx is
not only for Linux) and their texts should be held in a repository.

The only concern I have is accountability for accuracy of the license
repository.
*One possible* way to overcome this is, that we may specify what is a
standard compliant spdx license text repository as well. Then there can
be the default PURL repository (without warranty), but companies may
also host their own repository, and include to their spdx files a
pointer to that adress. (However if I say, this is a sdpx version x.y
compliant repository, I may not represent LGPL 2.1 as LGPL 3.0 in
there.)

Kind regards

Soeren Rabenstein

____________________________________________________________
?
ASUSTeK COMPUTER INC.
?
Soeren Rabenstein, LL.M.
Legal Affairs Center - Legal Compliance Dept.
15, Li-Te Rd., Taipei 112, Taiwan
Tel.: (+886) 2 2894 3447 Ext.2372
Fax.: (+886) 2 2890 7674
soeren_rabenstein@...
____________________________________________________________



========================================================================
=============================================================
This email and any attachments to it contain confidential information
and are intended solely for the use of the individual to whom it
is addressed.If you are not the intended recipient or receive it
accidentally, please immediately notify the sender by e-mail and delete
the message and any attachments from your computer system, and destroy
all hard copies. If any, please be advised that any unauthorized
disclosure, copying, distribution or any action taken or omitted in
reliance on this, is illegal and prohibited. Furthermore, any views
or opinions expressed are solely those of the author and do not
represent those of ASUSTeK. Thank you for your cooperation.
========================================================================
=============================================================



------------------------------

Message: 2
Date: Mon, 30 Aug 2010 09:25:28 +0200
From: Ciaran Farrell <cfarrell@...>
Subject: Some feedback I've received on the latest draft
To: spdx@...
Message-ID: <201008300925.28406.cfarrell@...>
Content-Type: text/plain; charset="utf-8"

Hi,

here is some feedback I received recently - I'm not sure how much of it
is
(still) relevant.

Ciaran

========================================================================
======
Page 4: 1.1 typo? "to share + and component"

Page 7: 2.2.7 stray capitalization? LicenseFInd

Page 14: 4.1.3 and 4.2.3 cardinality mandatory single instance

This seems incorrect, as the nonstandard license field is optional and
needed
only in case a nonstandard license is present.

"Should be present if" cannot map to "cardinality mandatory" in the
common use
of the term mandatory, which implies always, without if ands or buts.

Page 16: section 5

Cardinality mandatory is again used here, but the file list is not
present in
the tomcat examples on the site (nor, in my opinion, should be -- making
the
file list mandatory means making supplying these descriptions needlessly

harder. DOAP does not include mandatory file lists and it is the better
for
it, so neither should SPDX).

========================================================================
======

--
Ciaran Farrell __o
cfarrell@... _`\<,_
Phone: +49 (0)911 74053 262 (_)/ (_)
SUSE Linux Products GmbH,
GF: Markus Rex, HRB 16746 (AG N?rnberg)
Maxfeldstrasse 5, 90409, Nuremberg, Germany

/?ki?.r?n/


------------------------------

Message: 3
Date: Mon, 30 Aug 2010 14:53:38 +0200
From: Patrick MOREAU <Patrick.MOREAU@...>
Subject: CeCILL licences
To: "spdx@..." <spdx@...>
Message-ID:
<2F9743F08B7C8141BD6CB648C4304F1F44AAC42C05@...>
Content-Type: text/plain; charset="iso-8859-1"

Bonjour

I work in INRIA since 2009 and I follow all the exchanges about SPDX
specification.

I have read the V1.0 beta draft. This document seems very complete. I
have just one comment. We would like to mention also CeCILL licences
(http://www.cecill.info/licences.fr.html) that are used, at least, in
France.

I propose:

CeCILL-1.0
1.1. Formal Name: Ce(A)C(nrs)I(NRIA)L(ogiciel)L(ibre) V1
1.2. Official Download URL: http://www.cecill.info/licences.fr.html
1.3. SPDX Template Reference Copy: TBD

CeCILL-2.0
1.1. Formal Name: Ce(A)C(nrs)I(NRIA)L(ogiciel)L(ibre) V2
1.2. Official Download URL: http://www.cecill.info/licences.fr.html
1.3. SPDX Template Reference Copy: TBD

CeCILL-B-1.0
1.1. Formal Name: Ce(A)C(nrs)I(NRIA)L(ogiciel)L(ibre)-B
1.2. Official Download URL: http://www.cecill.info/licences.fr.html
1.3. SPDX Template Reference Copy: TBD

CeCILL-C-1.0
1.1. Formal Name: Ce(A)C(nrs)I(NRIA)L(ogiciel)L(ibre)-C
1.2. Official Download URL: http://www.cecill.info/licences.fr.html
1.3. SPDX Template Reference Copy: TBD

Best regards
Patrick


_________________________________________

Patrick Moreau
INRIA
Technology Transfer and Innovation Department
Software Assets Manager
Domaine de Voluceau - Rocquencourt
B.P. 105 - 78153 Le Chesnay Cedex
T?l: +33 1 39 63 78 40
Mob.: +33 6 77 84 58 15
Fax: +33 1 39 63 51 14
E-mail: patrick.moreau@...




------------------------------

Message: 4
Date: Mon, 30 Aug 2010 10:31:26 -0600
From: Peter Williams <peter.williams@...>
Subject: Re: Names of licenses we currently support / where should
licensetext live?
To: spdx@...
Message-ID: <4C7BDCDE.6060602@...>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 8/29/10 8:07 PM, Soeren_Rabenstein@... wrote:

The only concern I have is accountability for accuracy of the license
repository.
*One possible* way to overcome this is, that we may specify what is a
standard compliant spdx license text repository as well. Then there can
be the default PURL repository (without warranty), but companies may
also host their own repository, and include to their spdx files a
pointer to that adress. (However if I say, this is a sdpx version x.y
compliant repository, I may not represent LGPL 2.1 as LGPL 3.0 in
there.)

I can see some benefits to this approach. It will result in multiple
URIs for the same logical license, though. This might cause some
complications for certain classes of tools that consume SPDX. We could
overcome this by requiring that licenses in private repos provide a
isVersionOf[1] property whose value is the URI of the equivalent license

in the standard SPDX repo.

It is not clear to me that many organizations would need, or want, to
duplicate the main repo if it is maintained by an organization that can
credibly assert that once licenses are approved they are never modified.

However, supporting multiple repos is pretty easy.

Such functionality would also provide an organic way to grow the set of
standardized licenses. Licenses would start in private repos. Over
time the common ones would be approved into the main repo. Then private

repos could be update to indicate they are versions of the standardized
license.

Peter

[1]: http://dublincore.org/documents/dcmi-terms/#terms-isVersionOf


------------------------------

_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx


End of Spdx Digest, Vol 1, Issue 16
***********************************


Re: Names of licenses we currently support / where should licensetext live?

Peter Williams <peter.williams@...>
 

On 8/29/10 8:07 PM, Soeren_Rabenstein@... wrote:

The only concern I have is accountability for accuracy of the license repository.
*One possible* way to overcome this is, that we may specify what is a standard compliant spdx license text repository as well. Then there can be the default PURL repository (without warranty), but companies may also host their own repository, and include to their spdx files a pointer to that adress. (However if I say, this is a sdpx version x.y compliant repository, I may not represent LGPL 2.1 as LGPL 3.0 in there.)
I can see some benefits to this approach. It will result in multiple URIs for the same logical license, though. This might cause some complications for certain classes of tools that consume SPDX. We could overcome this by requiring that licenses in private repos provide a isVersionOf[1] property whose value is the URI of the equivalent license in the standard SPDX repo.

It is not clear to me that many organizations would need, or want, to duplicate the main repo if it is maintained by an organization that can credibly assert that once licenses are approved they are never modified. However, supporting multiple repos is pretty easy.

Such functionality would also provide an organic way to grow the set of standardized licenses. Licenses would start in private repos. Over time the common ones would be approved into the main repo. Then private repos could be update to indicate they are versions of the standardized license.

Peter

[1]: http://dublincore.org/documents/dcmi-terms/#terms-isVersionOf


CeCILL licences

Patrick MOREAU
 

Bonjour

I work in INRIA since 2009 and I follow all the exchanges about SPDX specification.

I have read the V1.0 beta draft. This document seems very complete. I have just one comment. We would like to mention also CeCILL licences (http://www.cecill.info/licences.fr.html) that are used, at least, in France.

I propose:

CeCILL-1.0
1.1. Formal Name: Ce(A)C(nrs)I(NRIA)L(ogiciel)L(ibre) V1
1.2. Official Download URL: http://www.cecill.info/licences.fr.html
1.3. SPDX Template Reference Copy: TBD

CeCILL-2.0
1.1. Formal Name: Ce(A)C(nrs)I(NRIA)L(ogiciel)L(ibre) V2
1.2. Official Download URL: http://www.cecill.info/licences.fr.html
1.3. SPDX Template Reference Copy: TBD

CeCILL-B-1.0
1.1. Formal Name: Ce(A)C(nrs)I(NRIA)L(ogiciel)L(ibre)-B
1.2. Official Download URL: http://www.cecill.info/licences.fr.html
1.3. SPDX Template Reference Copy: TBD

CeCILL-C-1.0
1.1. Formal Name: Ce(A)C(nrs)I(NRIA)L(ogiciel)L(ibre)-C
1.2. Official Download URL: http://www.cecill.info/licences.fr.html
1.3. SPDX Template Reference Copy: TBD

Best regards
Patrick


_________________________________________

Patrick Moreau
INRIA
Technology Transfer and Innovation Department
Software Assets Manager
Domaine de Voluceau - Rocquencourt
B.P. 105 - 78153 Le Chesnay Cedex
Tél: +33 1 39 63 78 40
Mob.: +33 6 77 84 58 15
Fax: +33 1 39 63 51 14
E-mail: patrick.moreau@...


Some feedback I've received on the latest draft

Ciaran Farrell
 

Hi,

here is some feedback I received recently - I'm not sure how much of it is
(still) relevant.

Ciaran

==============================================================================
Page 4: 1.1 typo? "to share + and component"

Page 7: 2.2.7 stray capitalization? LicenseFInd

Page 14: 4.1.3 and 4.2.3 cardinality mandatory single instance

This seems incorrect, as the nonstandard license field is optional and needed
only in case a nonstandard license is present.

"Should be present if" cannot map to "cardinality mandatory" in the common use
of the term mandatory, which implies always, without if ands or buts.

Page 16: section 5

Cardinality mandatory is again used here, but the file list is not present in
the tomcat examples on the site (nor, in my opinion, should be -- making the
file list mandatory means making supplying these descriptions needlessly
harder. DOAP does not include mandatory file lists and it is the better for
it, so neither should SPDX).

==============================================================================

--
Ciaran Farrell __o
cfarrell@... _`\<,_
Phone: +49 (0)911 74053 262 (_)/ (_)
SUSE Linux Products GmbH,
GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstrasse 5, 90409, Nuremberg, Germany

/ˈkiː.ræn/


Re: Names of licenses we currently support / where should licensetext live?

Soeren_Rabenstein@...
 

Peter Williams wrote:
Once a license is "approved" and placed in the repo it should be
immutable. That way there is no chance of the text changing once the
license name is in use.
I agree.
Also: If an spdx document is supposed to contain all the license texts, isn't there a danger that we end up documenting 10 KB of source code with 1 MB of license texts? (Yes I know, if there one thing America needs it's more license texts: http://www.youtube.com/watch?v=0u9JAt6gFqM).

Imho the spdx list of standard licenses should cover as many licenses as possible (whereas coverage of x % of the licenses in a common Linux Distribution is not necessarily the standard of completeness, as spdx is not only for Linux) and their texts should be held in a repository.

The only concern I have is accountability for accuracy of the license repository.
*One possible* way to overcome this is, that we may specify what is a standard compliant spdx license text repository as well. Then there can be the default PURL repository (without warranty), but companies may also host their own repository, and include to their spdx files a pointer to that adress. (However if I say, this is a sdpx version x.y compliant repository, I may not represent LGPL 2.1 as LGPL 3.0 in there.)

Kind regards

Soeren Rabenstein

____________________________________________________________
 
ASUSTeK COMPUTER INC.
 
Soeren Rabenstein, LL.M.
Legal Affairs Center - Legal Compliance Dept.
15, Li-Te Rd., Taipei 112, Taiwan
Tel.: (+886) 2 2894 3447 Ext.2372
Fax.: (+886) 2 2890 7674
soeren_rabenstein@...
____________________________________________________________



=====================================================================================================================================
This email and any attachments to it contain confidential information and are intended solely for the use of the individual to whom it
is addressed.If you are not the intended recipient or receive it accidentally, please immediately notify the sender by e-mail and delete
the message and any attachments from your computer system, and destroy all hard copies. If any, please be advised that any unauthorized
disclosure, copying, distribution or any action taken or omitted in reliance on this, is illegal and prohibited. Furthermore, any views
or opinions expressed are solely those of the author and do not represent those of ASUSTeK. Thank you for your cooperation.
=====================================================================================================================================


Re: Names of licenses we currently support / where should license text live?

Peter Williams <peter.williams@...>
 

On 8/27/10 2:47 PM, Jeff Luszcz wrote:
Hi Kate et al,
As we discussed on the call a few times, I think having this amazing list of license in one place is a great asset to the community and I believe will help reduce license proliferation (esp. if spdx.org, Linux foundation, OSI, etc... continue to work on anointing certain license as preferred.)

One of my concerns in having the SPDX document only contain links to these reference licenses instead of the actual full text is that we have the chance of drift and incompleteness a few years down the road, especially if the list of licenses we anointed as "reference license" becomes as large as it looks like it is becoming.

We see analogies to this in our day to day license analysis in these current cases:

Files that say "see License.txt file for more info" and the License.txt is missing
"See http://www.gnu.org/licenses/lgpl.html" in a file where this used to mean lgpl 2.1 in 2006, it now means lgpl 3.0 since the link target text was changed by the FSF
"Download from my university page http://www.ccsf.edu/~someStudent" which is now gone and no longer alive
"This is under a BSD license" when in fact they've added Copyleft style terms or other strange things to the actual license text.

My thoughts:
A SPDX doc should be completely self contained for long term validity, but can reference out to the spdx.org web site as a hook for optional data that may appear down the road
Some organizations have serious confidential concerns about outside web links/dependencies in Intellectual Property reports such as SPDX
By this I mean, if to render or validate the text of a license for a spdx report an organization has to hit the spdx.org website, this may cause leakage of confidential info
Having a large list of references licenses is great, especially if common names can be created for them
Template licenses / references are great for scanning tool verification / spec compliance etc but the SPDX doc should contain the actual text of the license in effect
Once a license is "approved" and placed in the repo it should be immutable. That way there is no chance of the text changing once the license name is in use.

To prevent links going defunct we could use PURL[1][2]. PURL is a permanent URL service provided under the auspices of the OCLC[3] (the library cooperative). PURL is widely used in the RDF, IETF and W3C communities for URIs that need to remain valid permanently.

Providing an optional way to embed the license text could still be useful. If we do allow an "approved" license to be specified along with it's license text the spec should clarify what the semantics are if the license text in the SPDX file doesn't match the license text of the named license in the license repo. Should it be treated as a custom license, and tools would ignore the specified license? Or should that constitute an error? Or should license text be ignore in favor of the license name?

Peter

[1]: http://purl.org
[2]: http://purl.oclc.org/docs/faq.html
[3]: http://oclc.org


Re: Names of licenses we currently support / where should license text live?

dmg
 

Jeff Luszcz twisted the bytes to say:


Jeff> Hi Kate et al,
As we discussed on the call a few times, I think having this amazing
list of license in one place is a great asset to the community and I
believe will help reduce license proliferation (esp. if spdx.org,
Linux foundation, OSI, etc... continue to work on anointing certain
license as preferred.)

Just a small comment. Our license identification tool has very different
goals than SPDX. We need to identify as many as we can (even those that
are references, and mark them as such).

In my view, SPDX should be good enough to document the majority of
MIT/BSD variants, plus the common licenses (GPL, LGPL, MPL, EPL). This,
in my opinion, should cover around 80-85 percent of files with a
license.

The problem lies on the MIT and BSD variants, and I think the SPDX
committee is being blind to that problem. I have made this point
repeatedly, so I will not push it any further.

Ultimately, somebody will have to write a filter that goes from
Fossology/Ninka to SPDX accepted licenses (and names) and their XML
format. With almost certainly, if a license is the SPDX list, Ninka will
be able to identify it.

--dmg


--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .


Re: Names of licenses we currently support / where should license text live?

Jeff Luszcz
 

Hi Kate et al,
As we discussed on the call a few times, I think having this amazing list of license in one place is a great asset to the community and I believe will help reduce license proliferation (esp. if spdx.org, Linux foundation, OSI, etc... continue to work on anointing certain license as preferred.)

One of my concerns in having the SPDX document only contain links to these reference licenses instead of the actual full text is that we have the chance of drift and incompleteness a few years down the road, especially if the list of licenses we anointed as "reference license" becomes as large as it looks like it is becoming.

We see analogies to this in our day to day license analysis in these current cases:

Files that say "see License.txt file for more info" and the License.txt is missing
"See http://www.gnu.org/licenses/lgpl.html" in a file where this used to mean lgpl 2.1 in 2006, it now means lgpl 3.0 since the link target text was changed by the FSF
"Download from my university page http://www.ccsf.edu/~someStudent" which is now gone and no longer alive
"This is under a BSD license" when in fact they've added Copyleft style terms or other strange things to the actual license text.

My thoughts:
A SPDX doc should be completely self contained for long term validity, but can reference out to the spdx.org web site as a hook for optional data that may appear down the road
Some organizations have serious confidential concerns about outside web links/dependencies in Intellectual Property reports such as SPDX
By this I mean, if to render or validate the text of a license for a spdx report an organization has to hit the spdx.org website, this may cause leakage of confidential info
Having a large list of references licenses is great, especially if common names can be created for them
Template licenses / references are great for scanning tool verification / spec compliance etc but the SPDX doc should contain the actual text of the license in effect


Regards,
Jeff

-----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On
Behalf Of kate.stewart@...
Sent: Thursday, August 26, 2010 4:30 PM
To: spdx@...; dmg@...
Subject: Re: Names of licenses we currently support

Thanks Daniel. As the reference page for each license and its header
emerge - cross checking against this is going to be useful.

Hmm, am a little concerned about putting some of them into the standard
set of reference licenses. ... in particular some I think should be
flagged as exceptions so they get looked at. ie. BeerWareV42 ;)
SameTermsAs and SeeFile are likely not licences but references to
licenses.

Can I assume that the mapping of names to the actual license search
strings can be found in Ninka sources?

In particular the BSD and MIT varients look worrisome. Any volunteers to
review the details there and make some recommendations?

Kate

--- On Thu, 8/26/10, D M German <dmg@...> wrote:

From: D M German <dmg@...>
Subject: Names of licenses we currently support
To: spdx@...
Date: Thursday, August 26, 2010, 5:39 PM

these the licenses we currently identify. Look particularly
at the BSDs
and MIts. Some are not licenses but their exception
statements. I have
the feeling that these cover around 75-86% of files in
Debian/Fedora
(the source code files that have a license)

--dmg



AGPLv3+
Apachev1.1
Apachev2
artifex
ArtisticLicensev1
autoConfException
BeerWareVer42
BindMITX11Var
BisonException
boost
boostV1
BSD1
BSD2
BSD2AdvInsteadOfBinary
BSD2aic700
BSD2EndorseInsteadOfBinary
BSD2SoftAndDoc
BSD2var1
BSD2var2
BSD3
BSD3NoWarranty
BSD4
BSD4NoEndor
BSDCairoStyleWarr
BSDdovecotStyle
BSDOnlyAdv
CDDLic
CDDLicV1
CDDLv1orGPLv2
Cecill
ClassPathException
CPLv0.5
CPLv1
dovecotSeeCopying
DoWhatTheFuckYouWantv2
emacsLic
EPLv1
FreeType
GhostscriptGPL
GPLnoVersion
GPLv1
GPLv1+
GPLv1orArtistic
GPLv2
GPLv2+
GPLv2orLGPLv2.1
GPLv2orv3
GPLv2orv3qtException
GPLv3
GPLv3+
IBMv1
intelBSDLicense
InterACPILic
kerberos
LesserGPLnoVersion
LesserGPLv2
LesserGPLv2+
LesserGPLv2.1
LesserGPLv2.1+
LesserGPLv3
LesserGPLv3+
LGPLv2
LGPLv2+
LGPLv2_1
LGPLv2.1
LGPLv2.1+
LGPLv2_1orv3
LGPLv2MISTAKE
LGPLv2+MISTAKE
LGPLv2orv3
LGPLv3
LGPLv3+
LibGCJLic
LibraryGPLv2
LibraryGPLv2+
LinkException
LinkExceptionBison
LinkExceptionGPL
LinkExceptionLeGPL
LinkExceptionOpenSSL
MITandGPL
MITCMU
MITCMUvar2
MITCMUvar3
MITmodern
MITold
MIToldMichiganVersion
MIToldwithoutSell
MIToldwithoutSellandNoDocumentationRequi
MIToldwithoutSellCMUVariant
MITVariant
MITX11BSDvar
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
MITX11simple
MPL1_1andLGPLv2_1
MPLGPL2orLGPLv2_1
MPL_LGPLsee
MPL-MIT-dual
MPLv1_0
MPLv1_1
MX4J
MX4JLicensev1
NCSA
NPLv1_0
NPLv1_1
openSSL
openSSLvar1
openSSLvar2
openSSLvar3
phpLicV3.01
Postfix
postgresql
publicDomain
QtGPLv2or3
QTv1
SameAsPerl
SameTermsAs
SeeFile
sequenceLic
SimpleLic
simpleLic
simpleLic2
simpleLicense1
SimpleOnlyKeepCopyright
SleepyCat
SSLeay
subversion
subversion+
subversionError
sunRPC
SunSimpleLic
svnkit
svnkit+
tmate+
W3CLic
WxException
X11
X11CMU
X11Festival
X11mit
zendv2
ZLIB
ZLIBref


--
--
Daniel M. German

http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx


Re: Names of licenses we currently support

dmg
 

kate> In particular the BSD and MIT varients look worrisome. Any
kate> volunteers to review the details there and make some
kate> recommendations?

If SPDX is interested, look at the data for postgresql that I send few
days ago. You'll see samples of the following licenses:

BSD2
BSD3
BSD3NoWarranty
BSDOnlyEndorseNoWarranty
GPLv2+,BisonException
MIToldwithoutSellandNoDocumentationRequi
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
postgresql
postgresqlRef
publicDomain
SameAsPerl

Perhaps Postgresql is a good example of a project to document using
SPDX. It is not too large, but it uses a fair number of licenses, some
well know, and some not.

kate> Kate

--
--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .


Re: Names of licenses we currently support

dmg
 

I agree, not all are licenses. Exceptions, for example, are treated as
a license, but to make sense, they have to accompany a
real one.

What I recommend people do, if really interested, is look at the
sources of posgresql (see my previous message) and see the different
variants of the BSD and MIT licenses we detect.

If you run ninka, look at each of the files it creates for a given
file analyzed. they will be very helpful in understanding our
identification.
of course, reading the paper helps.

--dmg

On Thu, Aug 26, 2010 at 4:30 PM, <kate.stewart@...> wrote:
Thanks Daniel.  As the reference page for each license and its header emerge - cross checking against this is going to be useful.

Hmm,  am a little concerned about putting some of them into the standard set of reference licenses.  ... in particular some I think should be flagged as exceptions so they get looked at.  ie. BeerWareV42   ;)
SameTermsAs and SeeFile are likely not licences but references to licenses.

Can I assume that the mapping of names to the actual license search strings can be found in Ninka sources?

In particular the BSD and MIT varients look worrisome.   Any volunteers to review the details there and make some recommendations?

Kate

--- On Thu, 8/26/10, D M German <dmg@...> wrote:

From: D M German <dmg@...>
Subject: Names of licenses we currently support
To: spdx@...
Date: Thursday, August 26, 2010, 5:39 PM

these the licenses we currently identify. Look particularly
at the BSDs
and MIts. Some are not licenses but their exception
statements. I have
the feeling that these cover around 75-86% of files in
Debian/Fedora
(the source code files that have a license)

--dmg



AGPLv3+
Apachev1.1
Apachev2
artifex
ArtisticLicensev1
autoConfException
BeerWareVer42
BindMITX11Var
BisonException
boost
boostV1
BSD1
BSD2
BSD2AdvInsteadOfBinary
BSD2aic700
BSD2EndorseInsteadOfBinary
BSD2SoftAndDoc
BSD2var1
BSD2var2
BSD3
BSD3NoWarranty
BSD4
BSD4NoEndor
BSDCairoStyleWarr
BSDdovecotStyle
BSDOnlyAdv
CDDLic
CDDLicV1
CDDLv1orGPLv2
Cecill
ClassPathException
CPLv0.5
CPLv1
dovecotSeeCopying
DoWhatTheFuckYouWantv2
emacsLic
EPLv1
FreeType
GhostscriptGPL
GPLnoVersion
GPLv1
GPLv1+
GPLv1orArtistic
GPLv2
GPLv2+
GPLv2orLGPLv2.1
GPLv2orv3
GPLv2orv3qtException
GPLv3
GPLv3+
IBMv1
intelBSDLicense
InterACPILic
kerberos
LesserGPLnoVersion
LesserGPLv2
LesserGPLv2+
LesserGPLv2.1
LesserGPLv2.1+
LesserGPLv3
LesserGPLv3+
LGPLv2
LGPLv2+
LGPLv2_1
LGPLv2.1
LGPLv2.1+
LGPLv2_1orv3
LGPLv2MISTAKE
LGPLv2+MISTAKE
LGPLv2orv3
LGPLv3
LGPLv3+
LibGCJLic
LibraryGPLv2
LibraryGPLv2+
LinkException
LinkExceptionBison
LinkExceptionGPL
LinkExceptionLeGPL
LinkExceptionOpenSSL
MITandGPL
MITCMU
MITCMUvar2
MITCMUvar3
MITmodern
MITold
MIToldMichiganVersion
MIToldwithoutSell
MIToldwithoutSellandNoDocumentationRequi
MIToldwithoutSellCMUVariant
MITVariant
MITX11BSDvar
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
MITX11simple
MPL1_1andLGPLv2_1
MPLGPL2orLGPLv2_1
MPL_LGPLsee
MPL-MIT-dual
MPLv1_0
MPLv1_1
MX4J
MX4JLicensev1
NCSA
NPLv1_0
NPLv1_1
openSSL
openSSLvar1
openSSLvar2
openSSLvar3
phpLicV3.01
Postfix
postgresql
publicDomain
QtGPLv2or3
QTv1
SameAsPerl
SameTermsAs
SeeFile
sequenceLic
SimpleLic
simpleLic
simpleLic2
simpleLicense1
SimpleOnlyKeepCopyright
SleepyCat
SSLeay
subversion
subversion+
subversionError
sunRPC
SunSimpleLic
svnkit
svnkit+
tmate+
W3CLic
WxException
X11
X11CMU
X11Festival
X11mit
zendv2
ZLIB
ZLIBref


--
--
Daniel M. German

http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx
--
--dmg

---
Daniel M. German
http://turingmachine.org


Re: Names of licenses we currently support

kate.stewart@...
 

Thanks Daniel. As the reference page for each license and its header emerge - cross checking against this is going to be useful.

Hmm, am a little concerned about putting some of them into the standard set of reference licenses. ... in particular some I think should be flagged as exceptions so they get looked at. ie. BeerWareV42 ;)
SameTermsAs and SeeFile are likely not licences but references to licenses.

Can I assume that the mapping of names to the actual license search strings can be found in Ninka sources?

In particular the BSD and MIT varients look worrisome. Any volunteers to review the details there and make some recommendations?

Kate

--- On Thu, 8/26/10, D M German <dmg@...> wrote:

From: D M German <dmg@...>
Subject: Names of licenses we currently support
To: spdx@...
Date: Thursday, August 26, 2010, 5:39 PM

these the licenses we currently identify. Look particularly
at the BSDs
and MIts. Some are not licenses but their exception
statements. I have
the feeling that these cover around 75-86% of files in
Debian/Fedora
(the source code files that have a license)

--dmg



AGPLv3+
Apachev1.1
Apachev2
artifex
ArtisticLicensev1
autoConfException
BeerWareVer42
BindMITX11Var
BisonException
boost
boostV1
BSD1
BSD2
BSD2AdvInsteadOfBinary
BSD2aic700
BSD2EndorseInsteadOfBinary
BSD2SoftAndDoc
BSD2var1
BSD2var2
BSD3
BSD3NoWarranty
BSD4
BSD4NoEndor
BSDCairoStyleWarr
BSDdovecotStyle
BSDOnlyAdv
CDDLic
CDDLicV1
CDDLv1orGPLv2
Cecill
ClassPathException
CPLv0.5
CPLv1
dovecotSeeCopying
DoWhatTheFuckYouWantv2
emacsLic
EPLv1
FreeType
GhostscriptGPL
GPLnoVersion
GPLv1
GPLv1+
GPLv1orArtistic
GPLv2
GPLv2+
GPLv2orLGPLv2.1
GPLv2orv3
GPLv2orv3qtException
GPLv3
GPLv3+
IBMv1
intelBSDLicense
InterACPILic
kerberos
LesserGPLnoVersion
LesserGPLv2
LesserGPLv2+
LesserGPLv2.1
LesserGPLv2.1+
LesserGPLv3
LesserGPLv3+
LGPLv2
LGPLv2+
LGPLv2_1
LGPLv2.1
LGPLv2.1+
LGPLv2_1orv3
LGPLv2MISTAKE
LGPLv2+MISTAKE
LGPLv2orv3
LGPLv3
LGPLv3+
LibGCJLic
LibraryGPLv2
LibraryGPLv2+
LinkException
LinkExceptionBison
LinkExceptionGPL
LinkExceptionLeGPL
LinkExceptionOpenSSL
MITandGPL
MITCMU
MITCMUvar2
MITCMUvar3
MITmodern
MITold
MIToldMichiganVersion
MIToldwithoutSell
MIToldwithoutSellandNoDocumentationRequi
MIToldwithoutSellCMUVariant
MITVariant
MITX11BSDvar
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
MITX11simple
MPL1_1andLGPLv2_1
MPLGPL2orLGPLv2_1
MPL_LGPLsee
MPL-MIT-dual
MPLv1_0
MPLv1_1
MX4J
MX4JLicensev1
NCSA
NPLv1_0
NPLv1_1
openSSL
openSSLvar1
openSSLvar2
openSSLvar3
phpLicV3.01
Postfix
postgresql
publicDomain
QtGPLv2or3
QTv1
SameAsPerl
SameTermsAs
SeeFile
sequenceLic
SimpleLic
simpleLic
simpleLic2
simpleLicense1
SimpleOnlyKeepCopyright
SleepyCat
SSLeay
subversion
subversion+
subversionError
sunRPC
SunSimpleLic
svnkit
svnkit+
tmate+
W3CLic
WxException
X11
X11CMU
X11Festival
X11mit
zendv2
ZLIB
ZLIBref


--
--
Daniel M. German           
     
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx


Names of licenses we currently support

dmg
 

these the licenses we currently identify. Look particularly at the BSDs
and MIts. Some are not licenses but their exception statements. I have
the feeling that these cover around 75-86% of files in Debian/Fedora
(the source code files that have a license)

--dmg



AGPLv3+
Apachev1.1
Apachev2
artifex
ArtisticLicensev1
autoConfException
BeerWareVer42
BindMITX11Var
BisonException
boost
boostV1
BSD1
BSD2
BSD2AdvInsteadOfBinary
BSD2aic700
BSD2EndorseInsteadOfBinary
BSD2SoftAndDoc
BSD2var1
BSD2var2
BSD3
BSD3NoWarranty
BSD4
BSD4NoEndor
BSDCairoStyleWarr
BSDdovecotStyle
BSDOnlyAdv
CDDLic
CDDLicV1
CDDLv1orGPLv2
Cecill
ClassPathException
CPLv0.5
CPLv1
dovecotSeeCopying
DoWhatTheFuckYouWantv2
emacsLic
EPLv1
FreeType
GhostscriptGPL
GPLnoVersion
GPLv1
GPLv1+
GPLv1orArtistic
GPLv2
GPLv2+
GPLv2orLGPLv2.1
GPLv2orv3
GPLv2orv3qtException
GPLv3
GPLv3+
IBMv1
intelBSDLicense
InterACPILic
kerberos
LesserGPLnoVersion
LesserGPLv2
LesserGPLv2+
LesserGPLv2.1
LesserGPLv2.1+
LesserGPLv3
LesserGPLv3+
LGPLv2
LGPLv2+
LGPLv2_1
LGPLv2.1
LGPLv2.1+
LGPLv2_1orv3
LGPLv2MISTAKE
LGPLv2+MISTAKE
LGPLv2orv3
LGPLv3
LGPLv3+
LibGCJLic
LibraryGPLv2
LibraryGPLv2+
LinkException
LinkExceptionBison
LinkExceptionGPL
LinkExceptionLeGPL
LinkExceptionOpenSSL
MITandGPL
MITCMU
MITCMUvar2
MITCMUvar3
MITmodern
MITold
MIToldMichiganVersion
MIToldwithoutSell
MIToldwithoutSellandNoDocumentationRequi
MIToldwithoutSellCMUVariant
MITVariant
MITX11BSDvar
MITX11noNotice
MITX11NoSellNoDocDocBSDvar
MITX11simple
MPL1_1andLGPLv2_1
MPLGPL2orLGPLv2_1
MPL_LGPLsee
MPL-MIT-dual
MPLv1_0
MPLv1_1
MX4J
MX4JLicensev1
NCSA
NPLv1_0
NPLv1_1
openSSL
openSSLvar1
openSSLvar2
openSSLvar3
phpLicV3.01
Postfix
postgresql
publicDomain
QtGPLv2or3
QTv1
SameAsPerl
SameTermsAs
SeeFile
sequenceLic
SimpleLic
simpleLic
simpleLic2
simpleLicense1
SimpleOnlyKeepCopyright
SleepyCat
SSLeay
subversion
subversion+
subversionError
sunRPC
SunSimpleLic
svnkit
svnkit+
tmate+
W3CLic
WxException
X11
X11CMU
X11Festival
X11mit
zendv2
ZLIB
ZLIBref


--
--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .


Ninka, on license names: an example

dmg
 

Some people have been asking for it. We finally have a pre-release. You
can download it from:

http://turingmachine.org/~dmg/temp/ninka-1.0-pre1.tar.bz2 (licensed AGPLv3)

I have discussed with Kate that I am going to start unifying names of
licenses with Fossology.

We decided to start looking at several projects, and see how
similar/different our identification is. Here is the first example:
postgresql. This is from the RPM of Fedora 12 (identical to Fedora 13, I
think). These are the "source code" files where we detected there is a
license.

contrib/pgcrypto/fortuna.c;BSD2
contrib/pgcrypto/fortuna.h;BSD2
contrib/pgcrypto/internal.c;BSD2
contrib/pgcrypto/internal-sha2.c;BSD2
contrib/pgcrypto/mbuf.c;BSD2
contrib/pgcrypto/mbuf.h;BSD2
contrib/pgcrypto/openssl.c;BSD2
contrib/pgcrypto/pgcrypto.c;BSD2
contrib/pgcrypto/pgcrypto.h;BSD2
contrib/pgcrypto/pgp-armor.c;BSD2
contrib/pgcrypto/pgp.c;BSD2
contrib/pgcrypto/pgp-cfb.c;BSD2
contrib/pgcrypto/pgp-compress.c;BSD2
contrib/pgcrypto/pgp-decrypt.c;BSD2
contrib/pgcrypto/pgp-encrypt.c;BSD2
contrib/pgcrypto/pgp.h;BSD2
contrib/pgcrypto/pgp-info.c;BSD2
contrib/pgcrypto/pgp-mpi.c;BSD2
contrib/pgcrypto/pgp-mpi-internal.c;BSD2
contrib/pgcrypto/pgp-mpi-openssl.c;BSD2
contrib/pgcrypto/pgp-pgsql.c;BSD2
contrib/pgcrypto/pgp-pubdec.c;BSD2
contrib/pgcrypto/pgp-pubenc.c;BSD2
contrib/pgcrypto/pgp-pubkey.c;BSD2
contrib/pgcrypto/pgp-s2k.c;BSD2
contrib/pgcrypto/px.c;BSD2
contrib/pgcrypto/px-crypt.c;BSD2
contrib/pgcrypto/px-crypt.h;BSD2
contrib/pgcrypto/px.h;BSD2
contrib/pgcrypto/px-hmac.c;BSD2
contrib/pgcrypto/random.c;BSD2
contrib/pgcrypto/crypt-des.c;BSD3
contrib/pgcrypto/md5.c;BSD3
contrib/pgcrypto/md5.h;BSD3
contrib/pgcrypto/sha1.c;BSD3
contrib/pgcrypto/sha1.h;BSD3
contrib/pgcrypto/sha2.c;BSD3
contrib/pgcrypto/sha2.h;BSD3
src/backend/port/dynloader/freebsd.c;BSD3
src/backend/port/dynloader/netbsd.c;BSD3
src/backend/port/dynloader/openbsd.c;BSD3
src/backend/utils/mb/wstrcmp.c;BSD3
src/backend/utils/mb/wstrncmp.c;BSD3
src/port/crypt.c;BSD3
src/port/getopt_long.c;BSD3
src/port/inet_aton.c;BSD3
src/port/memcmp.c;BSD3
src/port/qsort_arg.c;BSD3
src/port/qsort.c;BSD3
src/port/snprintf.c;BSD3
src/port/strtol.c;BSD3
src/port/strtoul.c;BSD3
src/port/getopt.c;BSD3NoWarranty
contrib/cube/cubeparse.c;GPLv2+,BisonException
contrib/seg/segparse.c;GPLv2+,BisonException
src/backend/bootstrap/bootparse.c;GPLv2+,BisonException
src/backend/parser/gram.c;GPLv2+,BisonException
src/backend/parser/gram.h;GPLv2+,BisonException
src/interfaces/ecpg/preproc/preproc.c;GPLv2+,BisonException
src/interfaces/ecpg/preproc/preproc.h;GPLv2+,BisonException
src/pl/plpgsql/src/pl_gram.c;GPLv2+,BisonException
src/pl/plpgsql/src/pl_gram.h;GPLv2+,BisonException
src/port/strlcat.c;MIToldwithoutSellandNoDocumentationRequi
src/port/strlcpy.c;MIToldwithoutSellandNoDocumentationRequi
contrib/pgcrypto/blf.c;MITX11noNotice
contrib/pgcrypto/blf.h;MITX11noNotice
contrib/pgcrypto/imath.c;MITX11noNotice
contrib/pgcrypto/imath.h;MITX11noNotice
src/backend/utils/adt/inet_net_ntop.c;MITX11NoSellNoDocDocBSDvar
src/backend/utils/adt/inet_net_pton.c;MITX11NoSellNoDocDocBSDvar
contrib/fuzzystrmatch/dmetaphone.c;postgresql
contrib/pageinspect/btreefuncs.c;postgresql
contrib/pgrowlocks/pgrowlocks.c;postgresql
contrib/pgstattuple/pgstatindex.c;postgresql
contrib/pgstattuple/pgstattuple.c;postgresql
src/port/gettimeofday.c;postgresql
src/bin/pg_dump/pg_backup_archiver.c;SeeFile
src/bin/pg_dump/pg_backup_archiver.h;SeeFile
src/bin/pg_dump/pg_backup_custom.c;SeeFile
src/bin/pg_dump/pg_backup_files.c;SeeFile
src/bin/pg_dump/pg_backup.h;SeeFile
src/bin/pg_dump/pg_backup_null.c;SeeFile
src/bin/pg_dump/pg_backup_tar.c;SeeFile
src/include/windowapi.h;SeeFile
src/test/thread/thread_test.c;SeeFile
src/pl/plperl/ppport.h;SeeFile,SameAsPerl
src/timezone/strftime.c;UNKNOWN [AllRights,0,,,,BSDpreLike,70,, the Univers=
ity of California, Berkeley,BSDcondEndorse,71,,,name of the University,BSDa=
sIs,80,,]
src/backend/regex/regc_color.c;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN=
,1,Redistribution and use in source and binary forms -- with or without mod=
ification -- are permitted for any purpose, provided that redistributions i=
n source form retain this entire copyright notice and indicate the origin a=
nd nature of any modifications,<------------>[Redistribution and use in sou=
rce and binary forms -- with or without modification -- are permitted for a=
ny purpose, provided that redistributions in source form retain this entire=
copyright notice and indicate the origin and nature of any modifications][=
],BSDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/backend/regex/regc_cvec.c;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,=
1,Redistribution and use in source and binary forms -- with or without modi=
fication -- are permitted for any purpose, provided that redistributions in=
source form retain this entire copyright notice and indicate the origin an=
d nature of any modifications,<------------>[Redistribution and use in sour=
ce and binary forms -- with or without modification -- are permitted for an=
y purpose, provided that redistributions in source form retain this entire =
copyright notice and indicate the origin and nature of any modifications][]=
,BSDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/backend/regex/regc_lex.c;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,1=
,Redistribution and use in source and binary forms -- with or without modif=
ication -- are permitted for any purpose, provided that redistributions in =
source form retain this entire copyright notice and indicate the origin and=
nature of any modifications,<------------>[Redistribution and use in sourc=
e and binary forms -- with or without modification -- are permitted for any=
purpose, provided that redistributions in source form retain this entire c=
opyright notice and indicate the origin and nature of any modifications][],=
BSDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/backend/regex/regc_nfa.c;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,1=
,Redistribution and use in source and binary forms -- with or without modif=
ication -- are permitted for any purpose, provided that redistributions in =
source form retain this entire copyright notice and indicate the origin and=
nature of any modifications,<------------>[Redistribution and use in sourc=
e and binary forms -- with or without modification -- are permitted for any=
purpose, provided that redistributions in source form retain this entire c=
opyright notice and indicate the origin and nature of any modifications][],=
BSDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/backend/regex/rege_dfa.c;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,1=
,Redistribution and use in source and binary forms -- with or without modif=
ication -- are permitted for any purpose, provided that redistributions in =
source form retain this entire copyright notice and indicate the origin and=
nature of any modifications,<------------>[Redistribution and use in sourc=
e and binary forms -- with or without modification -- are permitted for any=
purpose, provided that redistributions in source form retain this entire c=
opyright notice and indicate the origin and nature of any modifications][],=
BSDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/backend/regex/regerror.c;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,1=
,Redistribution and use in source and binary forms -- with or without modif=
ication -- are permitted for any purpose, provided that redistributions in =
source form retain this entire copyright notice and indicate the origin and=
nature of any modifications,<------------>[Redistribution and use in sourc=
e and binary forms -- with or without modification -- are permitted for any=
purpose, provided that redistributions in source form retain this entire c=
opyright notice and indicate the origin and nature of any modifications][],=
BSDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/backend/regex/regexec.c;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,1,=
Redistribution and use in source and binary forms -- with or without modifi=
cation -- are permitted for any purpose, provided that redistributions in s=
ource form retain this entire copyright notice and indicate the origin and =
nature of any modifications,<------------>[Redistribution and use in source=
and binary forms -- with or without modification -- are permitted for any =
purpose, provided that redistributions in source form retain this entire co=
pyright notice and indicate the origin and nature of any modifications][],B=
SDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/backend/regex/regfree.c;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,1,=
Redistribution and use in source and binary forms -- with or without modifi=
cation -- are permitted for any purpose, provided that redistributions in s=
ource form retain this entire copyright notice and indicate the origin and =
nature of any modifications,<------------>[Redistribution and use in source=
and binary forms -- with or without modification -- are permitted for any =
purpose, provided that redistributions in source form retain this entire co=
pyright notice and indicate the origin and nature of any modifications][],B=
SDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/include/regex/regcustom.h;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,=
1,Redistribution and use in source and binary forms -- with or without modi=
fication -- are permitted for any purpose, provided that redistributions in=
source form retain this entire copyright notice and indicate the origin an=
d nature of any modifications,<------------>[Redistribution and use in sour=
ce and binary forms -- with or without modification -- are permitted for an=
y purpose, provided that redistributions in source form retain this entire =
copyright notice and indicate the origin and nature of any modifications][]=
,BSDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/include/regex/regex.h;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,1,Re=
distribution and use in source and binary forms -- with or without modifica=
tion -- are permitted for any purpose, provided that redistributions in sou=
rce form retain this entire copyright notice and indicate the origin and na=
ture of any modifications,<------------>[Redistribution and use in source a=
nd binary forms -- with or without modification -- are permitted for any pu=
rpose, provided that redistributions in source form retain this entire copy=
right notice and indicate the origin and nature of any modifications][],BSD=
asIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/include/regex/regguts.h;UUNMATCHED [AllRights,0,,,,UNKNOWN,0,UNKNOWN,1,=
Redistribution and use in source and binary forms -- with or without modifi=
cation -- are permitted for any purpose, provided that redistributions in s=
ource form retain this entire copyright notice and indicate the origin and =
nature of any modifications,<------------>[Redistribution and use in source=
and binary forms -- with or without modification -- are permitted for any =
purpose, provided that redistributions in source form retain this entire co=
pyright notice and indicate the origin and nature of any modifications][],B=
SDasIs,70,,,<quotes>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
contrib/dblink/dblink.c;UUNMATCHED [AllRights-TOOLONG,0,pgsql/contrib/dblin=
k/dblink.c,v 1.82.2.2 2010/02/03 23<colon>01<colon>23 joe Exp $ Copyright (=
c) 2001-2009, PostgreSQL Global Development Group ,,,psql,10,,,UNKNOWN,0,UN=
KNOWN,1,IN NO EVENT SHALL THE AUTHOR OR DISTRIBUTORS BE LIABLE TO ANY PARTY=
FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLU=
DING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENT=
ATION, EVEN IF THE AUTHOR OR DISTRIBUTORS HAVE BEEN ADVISED OF THE POSSIBIL=
ITY OF SUCH DAMAGE,<------------>[IN NO EVENT SHALL THE AUTHOR OR DISTRIBUT=
ORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CO=
NSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS=
SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR OR DISTRIBUTORS HAVE BE=
EN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE][],psqlWarr,10,,,AUTHOR AND DI=
STRIBUTORS,psqlWarr2,10,,,THE AUTHOR AND DISTRIBUTORS]
contrib/dblink/dblink.h;UUNMATCHED [AllRights-TOOLONG,0,pgsql/contrib/dblin=
k/dblink.h,v 1.22 2009/06/09 17<colon>41<colon>02 tgl Exp $ Copyright (c) 2=
001-2009, PostgreSQL Global Development Group ,,,psql,10,,,UNKNOWN,0,UNKNOW=
N,1,IN NO EVENT SHALL THE AUTHOR OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR=
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING=
LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATIO=
N, EVEN IF THE AUTHOR OR DISTRIBUTORS HAVE BEEN ADVISED OF THE POSSIBILITY =
OF SUCH DAMAGE,<------------>[IN NO EVENT SHALL THE AUTHOR OR DISTRIBUTORS =
BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQ=
UENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOF=
TWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR OR DISTRIBUTORS HAVE BEEN A=
DVISED OF THE POSSIBILITY OF SUCH DAMAGE][],psqlWarr,10,,,AUTHOR AND DISTRI=
BUTORS,psqlWarr2,10,,,THE AUTHOR AND DISTRIBUTORS]
contrib/fuzzystrmatch/fuzzystrmatch.c;UUNMATCHED [AllRights-TOOLONG,0,pgsql=
/contrib/fuzzystrmatch/fuzzystrmatch.c,v 1.30.2.1 2009/12/10 01<colon>54<co=
lon>21 rhaas Exp $ Copyright (c) 2001-2009, PostgreSQL Global Development G=
roup ,,,psql,10,,,UNKNOWN,0,UNKNOWN,1,IN NO EVENT SHALL THE AUTHORS OR DIST=
RIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, =
OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF=
THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR OR DISTRIBUTORS HA=
VE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE,<------------>[IN NO EVEN=
T SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDI=
RECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS=
, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF TH=
E AUTHOR OR DISTRIBUTORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAG=
E][],UNKNOWN,0,UNKNOWN,1,THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM=
ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF M=
ERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,<------------>[THE AUTH=
ORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT N=
OT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A =
PARTICULAR PURPOSE][],psqlWarr2,10,,,THE AUTHOR AND DISTRIBUTORS]
contrib/pgbench/pgbench.c;UUNMATCHED [AllRights-TOOLONG,0,pgsql/contrib/pgb=
ench/pgbench.c,v 1.87.2.1 2009/07/30 09<colon>28<colon>05 mha Exp $ Copyrig=
ht (c) 2000-2009, PostgreSQL Global Development Group ,,,psql,10,,,UNKNOWN,=
0,UNKNOWN,1,IN NO EVENT SHALL THE AUTHOR OR DISTRIBUTORS BE LIABLE TO ANY P=
ARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, I=
NCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCU=
MENTATION, EVEN IF THE AUTHOR OR DISTRIBUTORS HAVE BEEN ADVISED OF THE POSS=
IBILITY OF SUCH DAMAGE,<------------>[IN NO EVENT SHALL THE AUTHOR OR DISTR=
IBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, O=
R CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF =
THIS SOFTWARE AND ITS DOCUMENTATION, EVEN IF THE AUTHOR OR DISTRIBUTORS HAV=
E BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE][],psqlWarr,10,,,AUTHOR AN=
D DISTRIBUTORS,psqlWarr2,10,,,THE AUTHOR AND DISTRIBUTORS]
contrib/tablefunc/tablefunc.c;UUNMATCHED [psql,10,,,UNKNOWN,0,UNKNOWN,1,IN =
NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIREC=
T, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST =
PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVE=
N IF THE AUTHOR OR DISTRIBUTORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUC=
H DAMAGE,<------------>[IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LI=
ABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTI=
AL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE=
AND ITS DOCUMENTATION, EVEN IF THE AUTHOR OR DISTRIBUTORS HAVE BEEN ADVISE=
D OF THE POSSIBILITY OF SUCH DAMAGE][],UNKNOWN,0,UNKNOWN,1,THE AUTHORS AND =
DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMIT=
ED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICUL=
AR PURPOSE,<------------>[THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAI=
M ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF =
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE][],psqlWarr2,10,,,THE =
AUTHOR AND DISTRIBUTORS]
contrib/tablefunc/tablefunc.h;UUNMATCHED [psql,10,,,UNKNOWN,0,UNKNOWN,1,IN =
NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIREC=
T, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST =
PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE AND ITS DOCUMENTATION, EVE=
N IF THE AUTHOR OR DISTRIBUTORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUC=
H DAMAGE,<------------>[IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LI=
ABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTI=
AL DAMAGES, INCLUDING LOST PROFITS, ARISING OUT OF THE USE OF THIS SOFTWARE=
AND ITS DOCUMENTATION, EVEN IF THE AUTHOR OR DISTRIBUTORS HAVE BEEN ADVISE=
D OF THE POSSIBILITY OF SUCH DAMAGE][],UNKNOWN,0,UNKNOWN,1,THE AUTHORS AND =
DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMIT=
ED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICUL=
AR PURPOSE,<------------>[THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAI=
M ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF =
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE][],psqlWarr2,10,,,THE =
AUTHOR AND DISTRIBUTORS]
src/include/utils/catcache.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,All cache fetc=
hes are done with indexscans (under normal conditions),<------------>[All c=
ache fetches are done with indexscans (under normal conditions)][]]
src/bin/psql/tab-complete.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Also it does no=
t always give you all the syntactically legal completions, only those that =
are the most common or the ones that the programmer felt most like implemen=
ting,<------------>[Also it does not always give you all the syntactically =
legal completions, only those that are the most common or the ones that the=
programmer felt most like implementing][]]
src/test/regress/sql/inherit.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,ALTER TABL=
E inhx add constraint foo CHECK (xx =3D <quotes>text<quotes>)
src/include/catalog/pg_amop.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,amoplefttype =
and amoprighttype are just copies of the operator<quotes>s oprleft/oprright=
, ie its declared input data types,<------------>[amoplefttype and amoprigh=
ttype are just copies of the operator<quotes>s oprleft/oprright, ie its dec=
lared input data types][]]
src/interfaces/libpq/fe-misc.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,As is, block=
and restart will cause repeat printouts,<------------>[As is, block and re=
start will cause repeat printouts][]]
src/backend/storage/ipc/procarray.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Because=
of various subtle race conditions it is critical that a backend hold the c=
orrect locks while setting or clearing its MyProc->xid field,<------------>=
[Because of various subtle race conditions it is critical that a backend ho=
ld the correct locks while setting or clearing its MyProc->xid field][]]
src/include/utils/portal.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Because the quer=
y rewriter does not allow arbitrary ON SELECT rewrite rules, only queries t=
hat were originally update-type could produce multiple plan trees
src/test/regress/sql/text.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,But as a spec=
ial exception for usability<quotes>s sake, we still allow implicit casting =
to text in concatenations, so long as the other input is text or an unknown=
literal,<------------>[But as a special exception for usability<quotes>s s=
ake, we still allow implicit casting to text in concatenations, so long as =
the other input is text or an unknown literal][]]
src/interfaces/ecpg/preproc/ecpg.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,(C) Mich=
ael Meskes <meskes@...> Feb 5th, 1998 Placed under the same lice=
nse as PostgreSQL,<------------>[(C) Michael Meskes <meskes@...>=
Feb 5th, 1998 Placed under the same license as PostgreSQL][]]
src/port/copydir.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,copydir.c copies a direc=
tory,<------------>[copydir.c copies a directory][]]
contrib/pgcrypto/rijndael.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Copyright in th=
is implementation is held by Dr B R Gladman but I hereby give permission fo=
r its free direct or derivative use subject to acknowledgment of its origin=
and compliance with any conditions that the originators of the algorithm p=
lace on its exploitation,<------------>[Copyright in this implementation is=
held by Dr B R Gladman but I hereby give permission for its free direct or=
derivative use subject to acknowledgment of its origin and compliance with=
any conditions that the originators of the algorithm place on its exploita=
tion][]]
contrib/pgcrypto/rijndael.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Copyright in th=
is implementation is held by Dr B R Gladman but I hereby give permission fo=
r its free direct or derivative use subject to acknowledgment of its origin=
and compliance with any conditions that the originators of the algorithm p=
lace on its exploitation,<------------>[Copyright in this implementation is=
held by Dr B R Gladman but I hereby give permission for its free direct or=
derivative use subject to acknowledgment of its origin and compliance with=
any conditions that the originators of the algorithm place on its exploita=
tion][]]
src/test/regress/sql/plancache.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,create f=
unction cachebug() returns void as $$ declare r int
src/test/regress/sql/triggers.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,CREATE FU=
NCTION trigger_func() RETURNS trigger LANGUAGE plpgsql AS <quotes> BEGIN RA=
ISE NOTICE <quotes>trigger_func() called<colon>,<------------>[CREATE FUNCT=
ION trigger_func() RETURNS trigger LANGUAGE plpgsql AS <quotes> BEGIN RAISE=
NOTICE <quotes>trigger_func() called<colon>][],UNKNOWN,0,UNKNOWN,1,create =
function trigtest() returns trigger as $$ begin raise notice <quotes>% % % =
%<quotes>, TG_RELNAME, TG_OP, TG_WHEN, TG_LEVEL
src/backend/catalog/information_schema.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,=
CREATE SCHEMA information_schema
src/pl/plperl/sql/plperl_trigger.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,define=
d $val) { elog(NOTICE, <quotes> $_TD-> {$key } =3D NULL<quotes>)
src/backend/executor/execProcnode.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,ExecIni=
tNode() notices that it is looking at a nest loop and as the code below dem=
onstrates, it calls ExecInitNestLoop(),<------------>[ExecInitNode() notice=
s that it is looking at a nest loop and as the code below demonstrates, it =
calls ExecInitNestLoop()][]]
src/test/regress/sql/dependency.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,GRANT S=
ELECT ON TABLE deptest TO GROUP regression_group
src/backend/catalog/system_views.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,GRANT =
SELECT, UPDATE ON pg_settings TO PUBLIC,<------------>[GRANT SELECT, UPDATE=
ON pg_settings TO PUBLIC][]]
src/test/regress/sql/numerology.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,GROUP B=
Y a result column name is not legal per SQL92, but we accept it anyway (if =
the name is not the name of any column exposed by FROM),<------------>[GROU=
P BY a result column name is not legal per SQL92, but we accept it anyway (=
if the name is not the name of any column exposed by FROM)][]]
src/interfaces/ecpg/include/sqlca.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,if <quo=
tes>W<quotes> a (hopefully) non-fatal notice occurred / 3<colon>,<---------=
--->[if <quotes>W<quotes> a (hopefully) non-fatal notice occurred / 3<colon=
][]]
src/test/regress/sql/polymorphism.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Legen=
d<colon>,<------------>[Legend<colon>][],UNKNOWN,0,UNKNOWN,1,test inlining =
of polymorphic SQL functions create function bleat(int) returns int as $$ b=
egin raise notice <quotes>bleat %<quotes>, $1
src/pl/plperl/sql/plperl_elog.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,my $msg =
=3D shift
src/backend/libpq/pqformat.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Note in partic=
ular the distinction between <quotes>raw data<quotes> and <quotes>text<quot=
es>
src/backend/executor/nodeAgg.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Notice that =
advance_transition_function() is coded to avoid a data copy step when the p=
revious transition value pointer is returned,<------------>[Notice that adv=
ance_transition_function() is coded to avoid a data copy step when the prev=
ious transition value pointer is returned][]]
src/backend/optimizer/geqo/geqo_copy.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Perm=
ission is hereby granted to copy all or any part of this program for free d=
istribution,<------------>[Permission is hereby granted to copy all or any =
part of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The autho=
r<quotes>s name and this copyright notice must be included in any copy,<---=
--------->[The author<quotes>s name and this copyright notice must be inclu=
ded in any copy][]]
src/backend/optimizer/geqo/geqo_cx.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Permis=
sion is hereby granted to copy all or any part of this program for free dis=
tribution,<------------>[Permission is hereby granted to copy all or any pa=
rt of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The author<=
quotes>s name and this copyright notice must be included in any copy,<-----=
------->[The author<quotes>s name and this copyright notice must be include=
d in any copy][]]
src/backend/optimizer/geqo/geqo_erx.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Permi=
ssion is hereby granted to copy all or any part of this program for free di=
stribution,<------------>[Permission is hereby granted to copy all or any p=
art of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The author=
<quotes>s name and this copyright notice must be included in any copy,<----=
-------->[The author<quotes>s name and this copyright notice must be includ=
ed in any copy][]]
src/backend/optimizer/geqo/geqo_mutation.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,=
Permission is hereby granted to copy all or any part of this program for fr=
ee distribution,<------------>[Permission is hereby granted to copy all or =
any part of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The a=
uthor<quotes>s name and this copyright notice must be included in any copy,=
<------------>[The author<quotes>s name and this copyright notice must be i=
ncluded in any copy][]]
src/backend/optimizer/geqo/geqo_ox1.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Permi=
ssion is hereby granted to copy all or any part of this program for free di=
stribution,<------------>[Permission is hereby granted to copy all or any p=
art of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The author=
<quotes>s name and this copyright notice must be included in any copy,<----=
-------->[The author<quotes>s name and this copyright notice must be includ=
ed in any copy][]]
src/backend/optimizer/geqo/geqo_ox2.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Permi=
ssion is hereby granted to copy all or any part of this program for free di=
stribution,<------------>[Permission is hereby granted to copy all or any p=
art of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The author=
<quotes>s name and this copyright notice must be included in any copy,<----=
-------->[The author<quotes>s name and this copyright notice must be includ=
ed in any copy][]]
src/backend/optimizer/geqo/geqo_pmx.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Permi=
ssion is hereby granted to copy all or any part of this program for free di=
stribution,<------------>[Permission is hereby granted to copy all or any p=
art of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The author=
<quotes>s name and this copyright notice must be included in any copy,<----=
-------->[The author<quotes>s name and this copyright notice must be includ=
ed in any copy][]]
src/backend/optimizer/geqo/geqo_px.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Permis=
sion is hereby granted to copy all or any part of this program for free dis=
tribution,<------------>[Permission is hereby granted to copy all or any pa=
rt of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The author<=
quotes>s name and this copyright notice must be included in any copy,<-----=
------->[The author<quotes>s name and this copyright notice must be include=
d in any copy][]]
src/backend/optimizer/geqo/geqo_selection.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1=
,Permission is hereby granted to copy all or any part of this program for f=
ree distribution,<------------>[Permission is hereby granted to copy all or=
any part of this program for free distribution][],UNKNOWN,0,UNKNOWN,1,The =
author<quotes>s name and this copyright notice must be included in any copy=
,<------------>[The author<quotes>s name and this copyright notice must be =
included in any copy][]]
src/bin/pg_dump/pg_dump.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,pg_dump will read=
the system catalogs in a database and dump out a script that reproduces th=
e schema in terms of SQL that is understood by PostgreSQL,<------------>[pg=
_dump will read the system catalogs in a database and dump out a script tha=
t reproduces the schema in terms of SQL that is understood by PostgreSQL][]]
src/bin/pg_dump/pg_restore.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,pg_restore wil=
l read the backup archive and dump out a script that reproduces the schema =
of the database in terms of user-defined types user-defined functions table=
s indexes aggregates operators ACL - grant/revoke,<------------>[pg_restore=
will read the backup archive and dump out a script that reproduces the sch=
ema of the database in terms of user-defined types user-defined functions t=
ables indexes aggregates operators ACL - grant/revoke][],UNKNOWN,0,UNKNOWN,=
1,Copyright (c) 2000, Philip Warner Rights are granted to use this software=
in any way so long as this notice is not removed,<------------>[Copyright =
(c) 2000, Philip Warner Rights are granted to use this software in any way =
so long as this notice is not removed][],UNKNOWN,0,UNKNOWN,1,The author is =
not responsible for loss or damages that may result from its use,<---------=
--->[The author is not responsible for loss or damages that may result from=
its use][]]
src/interfaces/ecpg/preproc/parse.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Placed=
under the same license as PostgreSQL,<------------>[Placed under the same =
license as PostgreSQL][]]
src/pl/plpython/sql/plpython_function.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,p=
lpy.notice(<quotes>import socket failed -- %s<quotes> % str(ex)) return <qu=
otes>failed as expected<quotes> return <quotes>succeeded, that wasn<quotes>=
t supposed to happen<quotes> LANGUAGE plpythonu,<------------>[plpy.notice(=
<quotes>import socket failed -- %s<quotes> % str(ex)) return <quotes>failed=
as expected<quotes> return <quotes>succeeded, that wasn<quotes>t supposed =
to happen<quotes> LANGUAGE plpythonu][],UNKNOWN,0,UNKNOWN,1,plpy.notice(<qu=
otes>import failed -- %s<quotes> % str(ex)) return <quotes>failed, that was=
n<quotes>t supposed to happen<quotes> return <quotes>succeeded, as expected=
<quotes> LANGUAGE plpythonu,<------------>[plpy.notice(<quotes>import faile=
d -- %s<quotes> % str(ex)) return <quotes>failed, that wasn<quotes>t suppos=
ed to happen<quotes> return <quotes>succeeded, as expected<quotes> LANGUAGE=
plpythonu][],UNKNOWN,0,UNKNOWN,1,val =3D TD[key] plpy.notice(<quotes>TD[<q=
uotes> + key + <quotes>] =3D> <quotes> + str(val)),<------------>[val =3D T=
D[key] plpy.notice(<quotes>TD[<quotes> + key + <quotes>] =3D> <quotes> + st=
r(val))][],UNKNOWN,0,UNKNOWN,1,plpy.notice(str(ex)) return None rv =3D plpy=
.execute(SD[<quotes>plan<quotes>], [ a ]) if len(rv)<colon>,<------------>[=
plpy.notice(str(ex)) return None rv =3D plpy.execute(SD[<quotes>plan<quotes=
], [ a ]) if len(rv)<colon>][]]
src/backend/nodes/read.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,read.c routines to=
convert a string (legal ascii representation of node) back to nodes,<-----=
------->[read.c routines to convert a string (legal ascii representation of=
node) back to nodes][]]
src/backend/regex/regcomp.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,re_comp and fri=
ends - compile REs This file includes several others (see the bottom),<----=
-------->[re_comp and friends - compile REs This file includes several othe=
rs (see the bottom)][],AllRights,0,,,,UNKNOWN,0,UNKNOWN,1,Redistribution an=
d use in source and binary forms -- with or without modification -- are per=
mitted for any purpose, provided that redistributions in source form retain=
this entire copyright notice and indicate the origin and nature of any mod=
ifications,<------------>[Redistribution and use in source and binary forms=
-- with or without modification -- are permitted for any purpose, provided=
that redistributions in source form retain this entire copyright notice an=
d indicate the origin and nature of any modifications][],BSDasIs,70,,,<quot=
es>,<quotes>,,BSDWarr,70,,,HENRY SPENCER,]
src/test/regress/sql/join.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,regression te=
st for improper extraction of OR indexqual conditions (as seen in early 8.3=
.x releases),<------------>[regression test for improper extraction of OR i=
ndexqual conditions (as seen in early 8.3.x releases)][]]
src/backend/utils/adt/selfuncs.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Restrictio=
n clause estimation<colon>,<------------>[Restriction clause estimation<col=
on>][],UNKNOWN,0,UNKNOWN,1,Join selectivity estimation is far more difficul=
t and usually less accurate than restriction estimation,<------------>[Join=
selectivity estimation is far more difficult and usually less accurate tha=
n restriction estimation][],UNKNOWN,0,UNKNOWN,1,When dealing with the inner=
scan of a nestloop join, we consider the join<quotes>s joinclauses as rest=
riction clauses for the inner relation, and treat vars of the outer relatio=
n as parameters (a/k/a constants of unknown values),<------------>[When dea=
ling with the inner scan of a nestloop join, we consider the join<quotes>s =
joinclauses as restriction clauses for the inner relation, and treat vars o=
f the outer relation as parameters (a/k/a constants of unknown values)][],U=
NKNOWN,0,UNKNOWN,1,So, restriction estimators need to be able to accept an =
argument telling which relation is to be treated as the variable,<---------=
--->[So, restriction estimators need to be able to accept an argument telli=
ng which relation is to be treated as the variable][],UNKNOWN,0,UNKNOWN,1,T=
he call convention for a restriction estimator (oprrest function) is,<-----=
------->[The call convention for a restriction estimator (oprrest function)=
is][]]
src/test/performance/runtests.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Script sho=
uldn<quotes>t notice either he is running for test or for initialization pu=
rposes,<------------>[Script shouldn<quotes>t notice either he is running f=
or test or for initialization purposes][]]
src/test/regress/sql/select_implicit.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,SE=
LECT_IMPLICIT Test cases for queries with ordering terms missing from the t=
arget list,<------------>[SELECT_IMPLICIT Test cases for queries with order=
ing terms missing from the target list][]]
src/port/strdup.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,strdup.c copies a null-te=
rminated string,<------------>[strdup.c copies a null-terminated string][]]
src/test/regress/sql/foreign_data.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Suppr=
ess NOTICE messages when roles don<quotes>t exist SET client_min_messages T=
O <quotes>error<quotes>,<------------>[Suppress NOTICE messages when roles =
don<quotes>t exist SET client_min_messages TO <quotes>error<quotes>][],UNKN=
OWN,0,UNKNOWN,1,no usage on FDW RESET ROLE
src/test/regress/sql/privileges.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Suppres=
s NOTICE messages when users/groups don<quotes>t exist SET client_min_messa=
ges TO <quotes>error<quotes>,<------------>[Suppress NOTICE messages when u=
sers/groups don<quotes>t exist SET client_min_messages TO <quotes>error<quo=
tes>][],UNKNOWN,0,UNKNOWN,1,GRANT ALL ON atest1 TO regressuser2
src/backend/postmaster/autovacuum.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,The aut=
ovacuum launcher cannot start the worker processes by itself, because doing=
so would cause robustness issues (namely, failure to shut them down on exc=
eptional conditions, and also, since the launcher is connected to shared me=
mory and is thus subject to corruption there, it is not as robust as the po=
stmaster),<------------>[The autovacuum launcher cannot start the worker pr=
ocesses by itself, because doing so would cause robustness issues (namely, =
failure to shut them down on exceptional conditions, and also, since the la=
uncher is connected to shared memory and is thus subject to corruption ther=
e, it is not as robust as the postmaster)][]]
src/backend/utils/cache/plancache.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,The cre=
ator of a cached plan can specify whether it is allowable for the query to =
change output tupdesc on replan (this could happen with <quotes>SELECT <quo=
tes> for example) if so, it<quotes>s up to the caller to notice changes and=
cope with them,<------------>[The creator of a cached plan can specify whe=
ther it is allowable for the query to change output tupdesc on replan (this=
could happen with <quotes>SELECT <quotes> for example) if so, it<quotes>s =
up to the caller to notice changes and cope with them][]]
src/backend/executor/nodeSetOp.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,The delive=
red output tuples are just copies of the first-to-arrive tuple in each inpu=
t group,<------------>[The delivered output tuples are just copies of the f=
irst-to-arrive tuple in each input group][]]
src/backend/regex/regc_locale.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,The followi=
ng terms apply to all files associated with the software unless explicitly =
disclaimed in individual files,<------------>[The following terms apply to =
all files associated with the software unless explicitly disclaimed in indi=
vidual files][],UNKNOWN,0,UNKNOWN,1,The authors hereby grant permission to =
use, copy, modify, distribute, and license this software and its documentat=
ion for any purpose, provided that existing copyright notices are retained =
in all copies and that this notice is included verbatim in any distribution=
s,<------------>[The authors hereby grant permission to use, copy, modify, =
distribute, and license this software and its documentation for any purpose=
, provided that existing copyright notices are retained in all copies and t=
hat this notice is included verbatim in any distributions][],UNKNOWN,0,UNKN=
OWN,1,No written agreement, license, or royalty fee is required for any of =
the authorized uses,<------------>[No written agreement, license, or royalt=
y fee is required for any of the authorized uses][],UNKNOWN,0,UNKNOWN,1,Mod=
ifications to this software may be copyrighted by their authors and need no=
t follow the licensing terms described here, provided that the new terms ar=
e clearly indicated on the first page of each file where they apply,<------=
------>[Modifications to this software may be copyrighted by their authors =
and need not follow the licensing terms described here, provided that the n=
ew terms are clearly indicated on the first page of each file where they ap=
ply][],UNKNOWN,0,UNKNOWN,1,IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE=
LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUE=
NTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, O=
R ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POS=
SIBILITY OF SUCH DAMAGE,<------------>[IN NO EVENT SHALL THE AUTHORS OR DIS=
TRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL,=
OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCU=
MENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISE=
D OF THE POSSIBILITY OF SUCH DAMAGE][],UNKNOWN,0,UNKNOWN,1,THE AUTHORS AND =
DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMIT=
ED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR =
PURPOSE, AND NON-INFRINGEMENT,<------------>[THE AUTHORS AND DISTRIBUTORS S=
PECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMP=
LIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND N=
ON-INFRINGEMENT][],UNKNOWN,0,UNKNOWN,1,THIS SOFTWARE IS PROVIDED ON AN <quo=
tes>AS IS<quotes> BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATIO=
N TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS,=
<------------>[THIS SOFTWARE IS PROVIDED ON AN <quotes>AS IS<quotes> BASIS,=
AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE=
, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS][],UNKNOWN,0,UNKNOWN,1,N=
otwithstanding the foregoing, the authors grant the U.S. Government and oth=
ers acting in its behalf permission to use and distribute the software in a=
ccordance with the terms specified in this license,<------------>[Notwithst=
anding the foregoing, the authors grant the U.S. Government and others acti=
ng in its behalf permission to use and distribute the software in accordanc=
e with the terms specified in this license][]]
src/backend/utils/init/flatfiles.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,The majo=
r restriction imposed by all that is that there<quotes>s no way to read an =
out-of-line-toasted datum, because the tuptoaster.c code is not prepared to=
cope with such an environment,<------------>[The major restriction imposed=
by all that is that there<quotes>s no way to read an out-of-line-toasted d=
atum, because the tuptoaster.c code is not prepared to cope with such an en=
vironment][]]
src/backend/executor/execTuples.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,These are=
used to ensure that the executor frees copies of tuples (made by ExecTarge=
tList) properly,<------------>[These are used to ensure that the executor f=
rees copies of tuples (made by ExecTargetList) properly][],UNKNOWN,0,UNKNOW=
N,1,CONVENIENCE INITIALIZATION ROUTINES ExecInitResultTupleSlot convenience=
routines to initialize ExecInitScanTupleSlot the various tuple slots for n=
odes ExecInitExtraTupleSlot / which store copies of tuples,<------------>[C=
ONVENIENCE INITIALIZATION ROUTINES ExecInitResultTupleSlot convenience rout=
ines to initialize ExecInitScanTupleSlot the various tuple slots for nodes =
ExecInitExtraTupleSlot / which store copies of tuples][]]
src/include/storage/spin.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,These macros are=
implemented in terms of hardware-dependent macros supplied by s_lock.h,<--=
---------->[These macros are implemented in terms of hardware-dependent mac=
ros supplied by s_lock.h][]]
src/test/regress/sql/transactions.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,They =
should not be able to see the partial results of the calling query,<-------=
----->[They should not be able to see the partial results of the calling qu=
ery][],UNKNOWN,0,UNKNOWN,1,But a volatile function can see the partial resu=
lts of the calling query create or replace function max_xacttest() returns =
smallint language sql as <quotes>select max(a) from xacttest<quotes> volati=
le,<------------>[But a volatile function can see the partial results of th=
e calling query create or replace function max_xacttest() returns smallint =
language sql as <quotes>select max(a) from xacttest<quotes> volatile][]]
src/bin/initdb/initdb.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This code is releas=
ed under the terms of the PostgreSQL License,<------------>[This code is re=
leased under the terms of the PostgreSQL License][]]
src/bin/pg_config/pg_config.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This code is =
released under the terms of the PostgreSQL License,<------------>[This code=
is released under the terms of the PostgreSQL License][]]
src/interfaces/ecpg/test/pg_regress_ecpg.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,=
This code is released under the terms of the PostgreSQL License,<----------=
-->[This code is released under the terms of the PostgreSQL License][]]
src/test/regress/pg_regress.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This code is =
released under the terms of the PostgreSQL License,<------------>[This code=
is released under the terms of the PostgreSQL License][]]
src/test/regress/pg_regress_main.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This cod=
e is released under the terms of the PostgreSQL License,<------------>[This=
code is released under the terms of the PostgreSQL License][]]
src/timezone/localtime.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This file is in th=
e public domain, so clarified as of 1996-06-05 by Arthur David Olson,<-----=
------->[This file is in the public domain, so clarified as of 1996-06-05 b=
y Arthur David Olson][]]
src/timezone/private.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This file is in the =
public domain, so clarified as of 1996-06-05 by Arthur David Olson,<-------=
----->[This file is in the public domain, so clarified as of 1996-06-05 by =
Arthur David Olson][]]
src/timezone/tzfile.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This file is in the p=
ublic domain, so clarified as of 1996-06-05 by Arthur David Olson,<--------=
---->[This file is in the public domain, so clarified as of 1996-06-05 by A=
rthur David Olson][]]
src/timezone/ialloc.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This file is in the p=
ublic domain, so clarified as of 2006-07-17 by Arthur David Olson,<--------=
---->[This file is in the public domain, so clarified as of 2006-07-17 by A=
rthur David Olson][]]
src/timezone/scheck.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This file is in the p=
ublic domain, so clarified as of 2006-07-17 by Arthur David Olson,<--------=
---->[This file is in the public domain, so clarified as of 2006-07-17 by A=
rthur David Olson][]]
src/timezone/zic.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This file is in the publ=
ic domain, so clarified as of 2006-07-17 by Arthur David Olson,<-----------=
->[This file is in the public domain, so clarified as of 2006-07-17 by Arth=
ur David Olson][]]
src/test/locale/test-ctype.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This is copyri=
ghted but free software,<------------>[This is copyrighted but free softwar=
e][],UNKNOWN,0,UNKNOWN,1,You can use it, modify and distribute in original =
or modified form providing that the author<quotes>s names and the above cop=
yright notice will remain,<------------>[You can use it, modify and distrib=
ute in original or modified form providing that the author<quotes>s names a=
nd the above copyright notice will remain][],UNKNOWN,0,UNKNOWN,1,Disclaimer=
, legal notice and absence of warranty,<------------>[Disclaimer, legal not=
ice and absence of warranty][],UNKNOWN,0,UNKNOWN,1,This software provided <=
quotes>as is<quotes> without any kind of warranty,<------------>[This softw=
are provided <quotes>as is<quotes> without any kind of warranty][]]
src/test/regress/sql/opr_sanity.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This is=
legal, but usually not intended,<------------>[This is legal, but usually =
not intended][],UNKNOWN,0,UNKNOWN,1,If oprrest is set, the operator must re=
turn boolean, and it must link to a proc with the right signature to be a r=
estriction selectivity estimator,<------------>[If oprrest is set, the oper=
ator must return boolean, and it must link to a proc with the right signatu=
re to be a restriction selectivity estimator][]]
src/backend/commands/async.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,This method is=
necessary because to avoid race conditions, we must hold lock on pg_listen=
er from when we insert a new listener tuple until we commit,<------------>[=
This method is necessary because to avoid race conditions, we must hold loc=
k on pg_listener from when we insert a new listener tuple until we commit][=
]]
contrib/dblink/sql/dblink.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,this time, <q=
uotes>cursor <quotes>rmt_foo_cursor<quotes> not found<quotes> as a notice S=
ELECT FROM dblink_fetch(<quotes>rmt_foo_cursor<quotes>,4,false) AS t(a int,=
b text, c text[]),<------------>[this time, <quotes>cursor <quotes>rmt_foo=
_cursor<quotes> not found<quotes> as a notice SELECT FROM dblink_fetch(<quo=
tes>rmt_foo_cursor<quotes>,4,false) AS t(a int, b text, c text[])][],UNKNOW=
N,0,UNKNOWN,1,CREATE FOREIGN DATA WRAPPER postgresql
src/backend/utils/adt/pg_lzcompress.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Thus,=
the decompressor simply copies rawsize bytes from the location after the h=
eader to the destination,<------------>[Thus, the decompressor simply copie=
s rawsize bytes from the location after the header to the destination][],UN=
KNOWN,0,UNKNOWN,1,Thus there are 3 stop conditions for the lookup of matche=
s<colon>,<------------>[Thus there are 3 stop conditions for the lookup of =
matches<colon>][]]
src/backend/optimizer/path/tidpath.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,tidpat=
h.c Routines to determine which TID conditions are usable for scanning a gi=
ven relation, and create TidPaths accordingly,<------------>[tidpath.c Rout=
ines to determine which TID conditions are usable for scanning a given rela=
tion, and create TidPaths accordingly][],UNKNOWN,0,UNKNOWN,1,What we are lo=
oking for here is WHERE conditions of the form <quotes>CTID =3D pseudoconst=
ant<quotes>, which can be implemented by just fetching the tuple directly v=
ia heap_fetch(),<------------>[What we are looking for here is WHERE condit=
ions of the form <quotes>CTID =3D pseudoconstant<quotes>, which can be impl=
emented by just fetching the tuple directly via heap_fetch()][],UNKNOWN,0,U=
NKNOWN,1,We can also handle OR<quotes>d conditions such as (CTID =3D const1=
) OR (CTID =3D const2), as well as ScalarArrayOpExpr conditions of the form=
CTID =3D ANY(pseudoconstant_array),<------------>[We can also handle OR<qu=
otes>d conditions such as (CTID =3D const1) OR (CTID =3D const2), as well a=
s ScalarArrayOpExpr conditions of the form CTID =3D ANY(pseudoconstant_arra=
y)][],UNKNOWN,0,UNKNOWN,1,We also support <quotes>WHERE CURRENT OF cursor<q=
uotes> conditions (CurrentOfExpr), which amount to <quotes>CTID =3D run-tim=
e-determined-TID<quotes>,<------------>[We also support <quotes>WHERE CURRE=
NT OF cursor<quotes> conditions (CurrentOfExpr), which amount to <quotes>CT=
ID =3D run-time-determined-TID<quotes>][]]
src/include/storage/pg_shmem.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,To simplify =
life for the SysV implementation, the ID is assumed to consist of two unsig=
ned long values (these are key and ID in SysV terms),<------------>[To simp=
lify life for the SysV implementation, the ID is assumed to consist of two =
unsigned long values (these are key and ID in SysV terms)][]]
src/test/regress/sql/rangefuncs.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,trigger=
s will fire, too create function noticetrigger() returns trigger as $$ begi=
n raise notice <quotes>noticetrigger % %<quotes>, new.f1, new.data
src/backend/utils/mb/Unicode/UCS_to_BIG5.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN,1=
,Unfortunately it is prohibited by the organization to distribute the map f=
iles,<------------>[Unfortunately it is prohibited by the organization to d=
istribute the map files][]]
src/backend/utils/mb/Unicode/UCS_to_EUC_CN.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN=
,1,Unfortunately it is prohibited by the organization to distribute the map=
files,<------------>[Unfortunately it is prohibited by the organization to=
distribute the map files][]]
src/backend/utils/mb/Unicode/UCS_to_EUC_JP.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN=
,1,Unfortunately it is prohibited by the organization to distribute the map=
files,<------------>[Unfortunately it is prohibited by the organization to=
distribute the map files][]]
src/backend/utils/mb/Unicode/UCS_to_EUC_KR.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN=
,1,Unfortunately it is prohibited by the organization to distribute the map=
files,<------------>[Unfortunately it is prohibited by the organization to=
distribute the map files][]]
src/backend/utils/mb/Unicode/UCS_to_EUC_TW.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN=
,1,Unfortunately it is prohibited by the organization to distribute the map=
files,<------------>[Unfortunately it is prohibited by the organization to=
distribute the map files][]]
src/backend/utils/mb/Unicode/UCS_to_GB18030.pl;UUNMATCHED [UNKNOWN,0,UNKNOW=
N,1,Unfortunately it is prohibited by the organization to distribute the ma=
p files,<------------>[Unfortunately it is prohibited by the organization t=
o distribute the map files][]]
src/backend/utils/mb/Unicode/UCS_to_most.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN,1=
,Unfortunately it is prohibited by the organization to distribute the map f=
iles,<------------>[Unfortunately it is prohibited by the organization to d=
istribute the map files][]]
src/backend/utils/mb/Unicode/UCS_to_SJIS.pl;UUNMATCHED [UNKNOWN,0,UNKNOWN,1=
,Unfortunately it is prohibited by the organization to distribute the map f=
iles,<------------>[Unfortunately it is prohibited by the organization to d=
istribute the map files][]]
src/include/storage/s_lock.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Usually, S_LOC=
K() is implemented in terms of an even lower-level macro TAS()<colon>,<----=
-------->[Usually, S_LOCK() is implemented in terms of an even lower-level =
macro TAS()<colon>][]]
src/pl/tcl/sql/pltcl_setup.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,$val<quotes>=
} set str <quotes>$str}<quotes> elog NOTICE <quotes>$key<colon>,<---------=
--->[$val<quotes> } set str <quotes>$str}<quotes> elog NOTICE <quotes>$key<=
colon>][],UNKNOWN,0,UNKNOWN,1,$str<quotes> } else { set val [eval list <quo=
tes> $$key<quotes> ] elog NOTICE <quotes>$key<colon>,<------------>[$str<qu=
otes> } else { set val [eval list <quotes> $$key<quotes> ] elog NOTICE <quo=
tes>$key<colon>][],UNKNOWN,0,UNKNOWN,1,This must be done AFTER the changes =
in T_pkey2 are done so the trigger for primkey check on T_dta2 fired on our=
updates will see the new key values in T_pkey2,<------------>[This must be=
done AFTER the changes in T_pkey2 are done so the trigger for primkey chec=
k on T_dta2 fired on our updates will see the new key values in T_pkey2][],=
UNKNOWN,0,UNKNOWN,1,Let old references follow and fire NOTICE message if th=
ere where some,<------------>[Let old references follow and fire NOTICE mes=
sage if there where some][],UNKNOWN,0,UNKNOWN,1,set n [spi_execp $GD(plan_d=
ta2_upd) [list $OLD(key1) $OLD(key2) $NEW(key1) $NEW(key2)]] if {$n > 0} { =
elog NOTICE <quotes>updated $n entries in T_dta2 for new key in T_pkey2<quo=
tes> } },<------------>[set n [spi_execp $GD(plan_dta2_upd) [list $OLD(key1=
) $OLD(key2) $NEW(key1) $NEW(key2)]] if {$n > 0} { elog NOTICE <quotes>upda=
ted $n entries in T_dta2 for new key in T_pkey2<quotes> } }][],UNKNOWN,0,UN=
KNOWN,1,delete references and fire NOTICE message if there where some,<----=
-------->[delete references and fire NOTICE message if there where some][],=
UNKNOWN,0,UNKNOWN,1,set n [spi_execp $GD(plan_dta2_del) [list $OLD(key1) $O=
LD(key2)]] if {$n > 0} { elog NOTICE <quotes>deleted $n entries from T_dta2=
<quotes> } },<------------>[set n [spi_execp $GD(plan_dta2_del) [list $OLD(=
key1) $OLD(key2)]] if {$n > 0} { elog NOTICE <quotes>deleted $n entries fro=
m T_dta2<quotes> } }][]]
src/test/regress/sql/select.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,VALUES is a=
lso legal as a standalone query or a set-operation member VALUES (1,2), (3,=
4+4), (7,77.7),<------------>[VALUES is also legal as a standalone query or=
a set-operation member VALUES (1,2), (3,4+4), (7,77.7)][]]
src/test/regress/sql/cluster.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Verify tha=
t clustering all tables does in fact cluster the right ones CREATE USER cls=
tr_user
src/test/regress/sql/portals.sql;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,We should =
not see the portal that is created internally to implement EXECUTE in pg_cu=
rsors PREPARE cprep AS SELECT name, statement, is_holdable, is_binary, is_s=
crollable FROM pg_cursors
src/backend/utils/hash/pg_crc.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,We use a no=
rmal (not <quotes>reflected<quotes>, in Williams<quotes> terms) CRC, using =
initial all-ones register contents and a final bit inversion,<------------>=
[We use a normal (not <quotes>reflected<quotes>, in Williams<quotes> terms)=
CRC, using initial all-ones register contents and a final bit inversion][]]
src/include/utils/pg_crc.h;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,We use a normal =
(not <quotes>reflected<quotes>, in Williams<quotes> terms) CRC, using initi=
al all-ones register contents and a final bit inversion,<------------>[We u=
se a normal (not <quotes>reflected<quotes>, in Williams<quotes> terms) CRC,=
using initial all-ones register contents and a final bit inversion][]]
src/backend/parser/scan.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,When we actually =
see the EOF, we change the status to <quotes>new<quotes> (via base_yyrestar=
t()), so that the user can continue scanning by just pointing base_yyin at =
a new input file,<------------>[When we actually see the EOF, we change the=
status to <quotes>new<quotes> (via base_yyrestart()), so that the user can=
continue scanning by just pointing base_yyin at a new input file][]]
src/backend/bootstrap/bootscanner.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,When we=
actually see the EOF, we change the status to <quotes>new<quotes> (via boo=
t_yyrestart()), so that the user can continue scanning by just pointing boo=
t_yyin at a new input file,<------------>[When we actually see the EOF, we =
change the status to <quotes>new<quotes> (via boot_yyrestart()), so that th=
e user can continue scanning by just pointing boot_yyin at a new input file=
][]]
contrib/cube/cubescan.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,When we actually se=
e the EOF, we change the status to <quotes>new<quotes> (via cube_yyrestart(=
)), so that the user can continue scanning by just pointing cube_yyin at a =
new input file,<------------>[When we actually see the EOF, we change the s=
tatus to <quotes>new<quotes> (via cube_yyrestart()), so that the user can c=
ontinue scanning by just pointing cube_yyin at a new input file][]]
src/backend/utils/misc/guc-file.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,When we a=
ctually see the EOF, we change the status to <quotes>new<quotes> (via GUC_y=
yrestart()), so that the user can continue scanning by just pointing GUC_yy=
in at a new input file,<------------>[When we actually see the EOF, we chan=
ge the status to <quotes>new<quotes> (via GUC_yyrestart()), so that the use=
r can continue scanning by just pointing GUC_yyin at a new input file][]]
src/pl/plpgsql/src/pl_scan.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,When we actual=
ly see the EOF, we change the status to <quotes>new<quotes> (via plpgsql_ba=
se_yyrestart()), so that the user can continue scanning by just pointing pl=
pgsql_base_yyin at a new input file,<------------>[When we actually see the=
EOF, we change the status to <quotes>new<quotes> (via plpgsql_base_yyresta=
rt()), so that the user can continue scanning by just pointing plpgsql_base=
_yyin at a new input file][]]
contrib/seg/segscan.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,When we actually see =
the EOF, we change the status to <quotes>new<quotes> (via seg_yyrestart()),=
so that the user can continue scanning by just pointing seg_yyin at a new =
input file,<------------>[When we actually see the EOF, we change the statu=
s to <quotes>new<quotes> (via seg_yyrestart()), so that the user can contin=
ue scanning by just pointing seg_yyin at a new input file][]]
src/bin/psql/psqlscan.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,When we actually se=
e the EOF, we change the status to <quotes>new<quotes> (via yyrestart()), s=
o that the user can continue scanning by just pointing yyin at a new input =
file,<------------>[When we actually see the EOF, we change the status to <=
quotes>new<quotes> (via yyrestart()), so that the user can continue scannin=
g by just pointing yyin at a new input file][]]
src/interfaces/ecpg/preproc/pgc.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,When we a=
ctually see the EOF, we change the status to <quotes>new<quotes> (via yyres=
tart()), so that the user can continue scanning by just pointing yyin at a =
new input file,<------------>[When we actually see the EOF, we change the s=
tatus to <quotes>new<quotes> (via yyrestart()), so that the user can contin=
ue scanning by just pointing yyin at a new input file][]]
src/backend/executor/nodeBitmapHeapscan.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,W=
ith SnapshotNow we might return a tuple that doesn<quotes>t meet the requir=
ed index qual conditions,<------------>[With SnapshotNow we might return a =
tuple that doesn<quotes>t meet the required index qual conditions][]]
contrib/pgcrypto/crypt-gensalt.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Written by=
Solar Designer and placed in the public domain,<------------>[Written by S=
olar Designer and placed in the public domain][]]
contrib/pgcrypto/crypt-blowfish.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Written b=
y Solar Designer <solar@...> in 1998-2001, and placed in the publi=
c domain,<------------>[Written by Solar Designer <solar@...> in 1=
998-2001, and placed in the public domain][],UNKNOWN,0,UNKNOWN,1,There<quot=
es>s absolutely no warranty,<------------>[There<quotes>s absolutely no war=
ranty][],UNKNOWN,0,UNKNOWN,1,I would appreciate it if you give credit where=
it is due and keep your modifications in the public domain as well, but I =
don<quotes>t require that in order to let you place this code and any modif=
ications you make under a license of your choice,<------------>[I would app=
reciate it if you give credit where it is due and keep your modifications i=
n the public domain as well, but I don<quotes>t require that in order to le=
t you place this code and any modifications you make under a license of you=
r choice][]]
contrib/sslinfo/sslinfo.c;UUNMATCHED [UNKNOWN,0,UNKNOWN,1,Written by Victor=
B. Wagner <vitus@...>, Cryptocom LTD This file is distributed und=
er BSD-style license,<------------>[Written by Victor B. Wagner <vitus@cryp=
tocom.ru>, Cryptocom LTD This file is distributed under BSD-style license][=
]]



--
--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .


LinuxCon2010 - BOF minutes - 2010/08/11

kate.stewart@...
 

Minutes - 2010/08/11 LinuxCon2010 Boston SPDX BOF

Current status:
- need to focus on goals for next 3 months
- SPDX.org rollout, shadows fossbazaar.org for data.
- mail list transfering to spdx@... with
self subscription to mail list now possible, and
public archives.
- package-facts@... now depreciated,
mail list there will remain private, per original
commitment.



Web site overview:
- site design is still evolving, participation welcome.
- log in to comment on wiki etc.
- anyone can blog on site, and postings on topic welcome.
- presentation material available on site for outreach support.
- AI: Phil/Martin - update on participation page where to join
(suggestion was to put link in text, not just at top,
consider "I want to use the spec, vs. I want to contribute
to the spec).
- AI: Kate to transfer document (.pdf) back to WIKI.
- AI: Phil update standard presentation with LinuxCon2010 input
- AI: Kate clean up the sharing analysis to what is accurate
- AI: Kate publish the current version number of the specification
in brackets behind reference.


- License Discussion:
- Look at Fedora's approach as a single page.
Example license text - canonical form.
Good from tooling perspective. Suck info off the pages.
HTML at low technical level is easy. RDF?
- see fedoraproject.org/wiki/License- licenses table.
- Used License Text - uses tag to identify in page
Fedora provide notes, and canonical text.
- For SPDX problem is where store templated version?
Suggestion is to use come up with standardized naming
of the sections, and embed the text of the licence
"template" version, so it shows up on the "official"
license page. (example to consider, verify that BSD
hasn't been modified and do it with a template).
- Fields to put on each "web license WIKI page"
- short form name
- long form name
- link to formal license
- notes on license
- full license text
- template version
- Note: need to figure out and document how to add a license
(ie. When you add a license - 1) create separate page;
raw template text, user visible text - here's out how
embed this text. etc.)
- AI: Tom to define a proposal for user front page.
Decide section names to correspond to spec
- AI: Group: discuss further following questions:
- what does it mean to be "on the list" for a license.
- what is it going to take to add and maintain a license.
- Consider when english isn't spoken language?
(what can be translated, what can't, work into template)

- roll out - operational aspects
- what do we want to get accomplished?
- divy out and how get accomplished?
- Target to have spec at 1.0 in 2010Q4
- What are building blocks needed?
Consider: documenting tooling; training; how to use.....
- Strong feeling one shot to get this right, want
free and comercial tool support available for supply chain.
- AI: Kim & John to work on operationalize plan.
(including a date can tell supply chain people?
GOAL is understand a date to have industry
changing/financially impacting. Tie to next LinuxCon??)


Re: Agenda for Aug 26 meeting

Clow, Marshall <mclow@...>
 

On Aug 25, 2010, at 6:52 AM, Philip Odence wrote:
Attached is the agenda. I've called out the logistical info separately.
I won't be attending this week, due to a conflict.

See you at the next meeting.

-- Marshall


Re: Agenda for Aug 26 meeting

Philip Odence
 

Forgot attachment.


Agenda for Aug 26 meeting

Philip Odence
 

Attached is the agenda. I've called out the logistical info separately.

Note: We are in flux with dial in numbers, so please check every time.

and Note: I am experimenting with using the Web log in to take attendance, so please plan to log in.

Meeting Time

Aug 26, 8am PDT / 10 am CDT / 11am EDT / 16:00 GMT

Conf call dial-in:

NOTE: THIS NUMBER IS DIFFERENT FROM PAST NUMBERS AND WILL BE CHANGING IN THE FUTURE.

Conference code:  7812589502

Toll-free dial-in number (U.S. and Canada):  (877) 435-0230

International dial-in number: (253) 336-6732

For those dialing in from other regions, a list of toll free numbers can be found: https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

Web

Note, we will be using a different URL for each meeting for purposes of taking attendance. - http://blackducksoftware.na6.acrobat.com/spdxaug26/



L. Philip Odence
Vice President of Business Development
Black Duck Software, inc.
265 Winter Street, Waltham, MA 02451
Phone: 781.810.1819, Mobile: 781.258.9502


Re: fossbazaar wiki and LinuxCon followup

Tom "spot" Callaway
 

On 08/24/2010 05:17 PM, Martin Michlmayr wrote:
* Tom spot Callaway <tcallawa@...> [2010-08-24 21:09]:
I should have left the answer to tbm who set it up.
Fair enough. :)

I'm still hopeful that there is some wiki intelligence in addition to
Drupal already present, and if not, I can make the case for us to move
to mediawiki. ;)
Bob's right. We're using Drupal and the Drupal wiki module.

What functionality do you need that's currently not there?
Well, there are a few things:

1. New page creation is really awkward.
2. There is no native wiki link syntax, so I would end up making a lot
of long URLs that aren't useful.
3. There is no native wiki section syntax, so I'd have to write a lot
more html than I'd prefer.
4. There is no wiki syntax for embedding one page in another. so I can't
really do what I've done in the mockup that I made on fedoraproject.org
(see my original email).
5. There are no default target mappings to sections (see #3), so I'd
have to hardcode them.

Drupal is a great CMS, but it is not such a great wiki.

~tom


Re: fossbazaar wiki and LinuxCon followup

Martin Michlmayr
 

* Tom spot Callaway <tcallawa@...> [2010-08-24 21:09]:
I should have left the answer to tbm who set it up.
Fair enough. :)

I'm still hopeful that there is some wiki intelligence in addition to
Drupal already present, and if not, I can make the case for us to move
to mediawiki. ;)
Bob's right. We're using Drupal and the Drupal wiki module.

What functionality do you need that's currently not there?
--
Martin Michlmayr
Open Source Program Office, Hewlett-Packard

1561 - 1580 of 1604