RE: [PATCH] Fix typo where the name SUN was split across two lines.

[gary]

Hi Mark, Brad, and SPDX legal team,

I don't think we every discussed the encoding standards for the XML files -
we have standardized on UTF-8 for the license text in the current
git.spdx.org licenses repo and the SPDX documents themselves.  I would
propose we standardize on UTF-8 for the XML as well to be consistent.

In terms of fixing the typo's, I'll coordinate with Jilayne on fixing (both
Jilayne and I have commit access to the git.spdx.org licenses repo).

Gary

> -Original Message-
> From: spdx-legal-boun...@lists.spdx.org [mailto:spdx-legal-
> boun...@lists.spdx.org] On Behalf Of Mark D. Baushke
> Sent: Friday, October 7, 2016 9:33 AM
> To: Brad Edmondson
> Cc: SPDX Legal
> Subject: Re: [PATCH] Fix typo where the name SUN was split across two
> lines.
> 
> Hi Brad,
> 
> As no documentation (other than searching the mailing list archive) on
> the spdx.org site seems to point to github right now, I think it would
> be best if someone could fix git.spdx.org sooner than later.
> 
> I would very much like to see both typos you mention fixed.
> 
> Regarding https://github.com/spdx/license-list-XML
> 
> Are we to assume that all of these are using an encodeing="ISO8859-1"
> 
> I am uncertain if there is any instanes of Unicode 'COPYRIGHT SIGN'
> (U+00A9) being encoded as either hex (0xc2, 0xa9) or just hex (0xa9) as
> I have found in some source files. (I already expect to see it as (c),
> (C), and  in various files...)
> 
>   Thanks,
>   -- Mark
> ___
> Spdx-legal mailing list
> Spdx-legal@lists.spdx.org
> https://lists.spdx.org/mailman/listinfo/spdx-legal

___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

Re: [PATCH] Fix typo where the name SUN was split across two lines.

[Brad Edmondson]

Thanks Mark, I think you have the right idea with that perspective.

Also, please note that the GH files are NOT STABLE in structure or in
substantive content at this point, so you're right to continue to look to
spdx.org for authoritative files.

Best,
Brad

--
Brad Edmondson, *Esq.*
512-673-8782 | brad.edmond...@gmail.com

On Fri, Oct 7, 2016 at 12:33 PM, Mark D. Baushke  wrote:

> Hi Brad,
>
> As no documentation (other than searching the mailing list archive) on
> the spdx.org site seems to point to github right now, I think it would
> be best if someone could fix git.spdx.org sooner than later.
>
> I would very much like to see both typos you mention fixed.
>
> Regarding https://github.com/spdx/license-list-XML
>
> Are we to assume that all of these are using an encodeing="ISO8859-1"
>
> I am uncertain if there is any instanes of Unicode 'COPYRIGHT SIGN'
> (U+00A9) being encoded as either hex (0xc2, 0xa9) or just hex (0xa9) as
> I have found in some source files. (I already expect to see it as (c),
> (C), and  in various files...)
>
> Thanks,
> -- Mark
>
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

Re: [PATCH] Fix typo where the name SUN was split across two lines.

[Mark D. Baushke]

Hi Brad,

As no documentation (other than searching the mailing list archive) on
the spdx.org site seems to point to github right now, I think it would
be best if someone could fix git.spdx.org sooner than later.

I would very much like to see both typos you mention fixed.

Regarding https://github.com/spdx/license-list-XML

Are we to assume that all of these are using an encodeing="ISO8859-1"

I am uncertain if there is any instanes of Unicode 'COPYRIGHT SIGN'
(U+00A9) being encoded as either hex (0xc2, 0xa9) or just hex (0xa9) as
I have found in some source files. (I already expect to see it as (c),
(C), and  in various files...)

Thanks,
-- Mark
___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

RE: HPND & NTP

[Wheeler, David A]

Jilayne’s recommendation makes sense to me…!

--- David A. Wheeler


From: spdx-tech-boun...@lists.spdx.org 
[mailto:spdx-tech-boun...@lists.spdx.org] On Behalf Of J Lovejoy
Sent: Friday, October 07, 2016 4:21 AM
To: SPDX-legal
Cc: spdx-t...@lists.spdx.org
Subject: HPND & NTP

Hi All,

During the SPDX bake-off it came up that NTP https://spdx.org/licenses/NTP.html 
can match to HPND https://spdx.org/licenses/HPND.html due to the template 
nature of HPND.  The folks in the bakeoff wanted to know if we ought to 
deprecate one of these licenses in favor of using the other or how a tool 
should reconcile which license to “pick” where both could be a valid answer.  
Talking about this here in Berlin and looking at the licenses, can we please 
discuss the following items on the next legal call:

1) Both of these licenses are OSI-approved, which is why they are both on the 
SPDX License List. Given that we endeavor to have all OSI-approved licenses on 
the SPDX License List (even if they are old or have been voluntarily deprecated 
by the author, as has HPND), so I don’t view deprecation as an option.  All 
agree?

2) As to HPND, we did not have markup for this license, but it needs it - Sam 
has added markup to the XML template and Brad has reviewed. It is flagged for 
review by the legal team: 
https://github.com/spdx/license-list-XML/pull/89/files  - can we get another 
set of eyes on this, both from the legal perspective and to check the markup?

3) OSI has comments as to how to “match” this license at the bottom of their 
page - 
https://opensource.org/licenses/HPNDl - 
should we add this to the Notes field, as is suggested in the XML file (do we 
really need it, especially if we have the markup and since the line about white 
space and capitalization merely repeats a couple of our matching guidelines?)

4) I would recommend adding a comment in the Notes field for each license along 
the lines of the following:
- for NTP: "This license is the same as HPND, when taking into consideration 
the templatizing options given in that license.  This is included as a separate 
license on the SPDX License List because it is separately approved by the OSI.”

- HPND: “Due to the templatization options of this license, it can be the same 
text as NTP license. This is included as a separate license on the SPDX License 
List because it is separately approved by the OSI.”

Please edit as needed.  Perhaps we can then ask the OSI to add similar language 
on their pages as well, so it is all consistent.


Thanks,
Jilayne


SPDX Legal Team co-lead
opensou...@jilayne.com

___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal

HPND & NTP

[J Lovejoy]

Hi All,

During the SPDX bake-off it came up that NTP https://spdx.org/licenses/NTP.html 
 can match to HPND 
https://spdx.org/licenses/HPND.html  due 
to the template nature of HPND.  The folks in the bakeoff wanted to know if we 
ought to deprecate one of these licenses in favor of using the other or how a 
tool should reconcile which license to “pick” where both could be a valid 
answer.  Talking about this here in Berlin and looking at the licenses, can we 
please discuss the following items on the next legal call:

1) Both of these licenses are OSI-approved, which is why they are both on the 
SPDX License List. Given that we endeavor to have all OSI-approved licenses on 
the SPDX License List (even if they are old or have been voluntarily deprecated 
by the author, as has HPND), so I don’t view deprecation as an option.  All 
agree?

2) As to HPND, we did not have markup for this license, but it needs it - Sam 
has added markup to the XML template and Brad has reviewed. It is flagged for 
review by the legal team: 
https://github.com/spdx/license-list-XML/pull/89/files 
  - can we get another 
set of eyes on this, both from the legal perspective and to check the markup? 

3) OSI has comments as to how to “match” this license at the bottom of their 
page - https://opensource.org/licenses/HPND 
l  - 
should we add this to the Notes field, as is suggested in the XML file (do we 
really need it, especially if we have the markup and since the line about white 
space and capitalization merely repeats a couple of our matching guidelines?)

4) I would recommend adding a comment in the Notes field for each license along 
the lines of the following:
- for NTP: "This license is the same as HPND, when taking into consideration 
the templatizing options given in that license.  This is included as a separate 
license on the SPDX License List because it is separately approved by the OSI.”

- HPND: “Due to the templatization options of this license, it can be the same 
text as NTP license. This is included as a separate license on the SPDX License 
List because it is separately approved by the OSI.”

Please edit as needed.  Perhaps we can then ask the OSI to add similar language 
on their pages as well, so it is all consistent.


Thanks,
Jilayne


SPDX Legal Team co-lead
opensou...@jilayne.com


___
Spdx-legal mailing list
Spdx-legal@lists.spdx.org
https://lists.spdx.org/mailman/listinfo/spdx-legal