Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:12
    Blackclaws commented #726
  • 14:10
    Blackclaws commented #2885
  • 08:58

    pombredanne on improve-gradle

    Improve Gradle script handling … (compare)

  • 04:36
    rohitcoder starred nexB/scancode-toolkit
  • 01:11
    JonoYang synchronize #2974
  • 01:11

    JonoYang on 2972-summary-consider-copyrights

    Do not use party members as dec… Get canonical version of holder… Use detected holders from packa… (compare)

  • May 23 21:48
    martonilles starred nexB/scancode-toolkit
  • May 23 21:37
    johnmhoran labeled #2976
  • May 23 21:37
    johnmhoran labeled #2976
  • May 23 21:37
    johnmhoran opened #2976
  • May 23 21:06
    pombredanne commented #2975
  • May 23 21:05
    rspier commented #2975
  • May 23 21:03
    pombredanne commented #2878
  • May 23 21:02
    pombredanne opened #2975
  • May 23 19:59
    johnmhoran synchronize #2958
  • May 23 19:59

    johnmhoran on 2945-file-cat

    Include directories in codebase… (compare)

  • May 23 17:36
    JonoYang closed #2967
  • May 23 17:36
    JonoYang commented #2967
  • May 23 15:46
    johnmhoran synchronize #2958
  • May 23 15:46

    johnmhoran on 2945-file-cat

    Add initial JSON-based test Re… (compare)

Henrik Sandklef
@hesa
Whatever we call it, I would like to license-expression to be able to go from "GPLv2" to "GPL-2.0-only" :)
Philippe Ombredanne
@pombredanne
@hesa actually, adding a list of alias to each license record may be the best
https://github.com/maxhbr/LDBcollector/issues/4#
this way they are closest together
and license-expression would just consume this
Philippe Ombredanne
@pombredanne
@hesa at some stage I would also like to integrate flict in scancode.io :)
1 reply
separate topic :)
Henrik Sandklef
@hesa
@pombredanne I am not sure how to add an "alias". Will this be a new concept in scancode? If so, I'll propose some syntax. If "alias" is already a concept, please show me an example :)
Maximilian Huber
@maxhbr
Henrik Sandklef
@hesa
@maxhbr The column "True", sometimes with the value "False" :), what is it for?
Henrik Sandklef
@hesa
@maxhbr Have these aliases been verified? E.g. X11 is in the table linked above an alias for ICU, but the license text differ although similar, so I am curious what a lawyer would say. Note: I would love to see more aliases in license-expression and your list is impressive :)
From a license compatibility point of view, they're compatible ("the same"), but not when attributing the license (text)?
Maximilian Huber
@maxhbr
The third column indicates whether that is a unique mapping. So if the same alias appears to be mapped to multiple licenses or was flagged ambiguous in the beginning, it is set to "False"
Henrik Sandklef
@hesa
Ah nice
Maximilian Huber
@maxhbr
The x11 / ICU clash comes from the scancode data and was already discussed in https://github.com/maxhbr/LDBcollector/issues/4#
Henrik Sandklef
@hesa
Yes. I am curious if the list of aliases can be used in license-expression (by first adding it to https://github.com/nexB/scancode-toolkit/tree/develop/src/licensedcode/data/licenses).

Looking at the scancode files:
$ head -7 x11.yml
key: x11
short_name: X11 License
name: X11 License
category: Permissive
owner: XFree86 Project, Inc
homepage_url: http://www.xfree86.org/3.3.6/COPYRIGHT2.html
spdx_license_key: ICU

Is this the origin of "your" circular alias?

Maximilian Huber
@maxhbr
yes
in the SPXD list, X11 and ICU are two independent licenses, and this joins these two. this violates the rule that the main IDs never have clashes with aliases ...
Henrik Sandklef
@hesa
Hmmm... OK :(
Philippe Ombredanne
@pombredanne

If "alias" is already a concept, please show me an example :)

an alias is something in license-expression, but not in scancode. IMHO this would be a list of strings naned aliases

3 replies
Philippe Ombredanne
@pombredanne

@maxhbr re:

The LDBcollector allready has these aliases: https://github.com/maxhbr/LDBcollector/blob/generated/aliases/aliases.csv#L686

This would be perfect!

Philippe Ombredanne
@pombredanne

@maxhbr @hesa re:

The x11 / ICU clash comes from the scancode data and was already discussed in https://github.com/maxhbr/LDBcollector/issues/4#

I would rather say that SPDX got it differently possibly not right.
But basically:

  1. what scancode calls x11 and SPDX calls ICU originated at X11 not ICU. It is mapped to SPDX ICU alright in SC data.
  2. what scancode calls x11-xconsortium and SPDX call X11 is really specific to the X consortium. It is mapped to SPDX X11 alright in SC data.

But I reckon this may need some thinking wrt. to use as aliases. The simplest may be to ignore the scancode key in the set of license symbols and only use SPDX and aliases

This message was deleted
@hesa if you like to join there is a weekly call starting at https://meet.jit.si/AboutCode now
3 replies
Ayan Sinha Mahapatra
@AyanSinhaMahapatra
Philippe Ombredanne
@pombredanne
thx
Aditya Sangave
@adii21-Ux
Hi everyone I am Aditya an undergrad student from India, I just finished setting up my development environment for scancode because I want to contribute to this project and I am good with python, django, html, css and ready to contribute so if there are any issues I can work on to understand codebase please let me know.
Aditya Sangave
@adii21-Ux
Hello I was going through scancode-toolkit documentation and here (https://scancode-toolkit.readthedocs.io/en/latest/getting-started/newcomer.html) I found that there are these three points about scan which are repeated in two section namely Try Scancode Toolkit and Installing Scancode and I don't think its necessary in both topics.
Philippe Ombredanne
@pombredanne
@adii21-Ux good catch :) the doc needs some significant love alright (much more than just a few typos)
Aditya Sangave
@adii21-Ux
should I fix this and open a PR?
Philippe Ombredanne
@pombredanne
@adii21-Ux sure thing, and having something that touches code and not just doc is always welcomed too
Aditya Sangave
@adii21-Ux
ok, I'll make sure if I can do some other changes
Mike Rombout
@mrombout

I am having a bit of trouble understanding Query.unknown_by_pos. As far as I can tell the query tests/licensedcode/data/datadriven/external/fossology-tests/BSD/lz4.license.txt matches the rule src/licensedcode/data/rules/bsd-simplified_and_gpl-2.0_1.RULE exactly (apart from everything after line 7). Yet in the refine_matches phase (second iteration) it reports the following unknowns_by_pos = defaultdict(<class 'int'>, {43: 0, 41: 0, 15: 0, 21: 0, 20: 0}), I am particularly surprised by 15, 20 and 21. And this is throwing off #2637.

I was under the impression that token will be considered unknown if token not in query.idx.dictionary? But it is not that simple?

20 replies
Mike Rombout
@mrombout

I'm afraid I have another case that I'm not able to work out. Another one where the ispan is too inclusive: https://github.com/softsense/scancode-toolkit/blob/issue-2637-allow-license-rules-to-require-the-presence-of-certain-defining-keywords/tests/licensedcode/test_match.py#L325

The ispan of the match containsSpan(2,22), but I feel it should be Span(2,4)|Span(7...) so that it does not include the key phrase of Span(2,8)

Philippe Ombredanne
@pombredanne
@mrombout hey :wave: ...let me check.
Philippe Ombredanne
@pombredanne
@mrombout https://github.com/softsense/scancode-toolkit/pull/1/files#r758425422 you are being misled by the weirdness that may exist in very small indexes
and may be the actual nature of what is in an ispan?
Mike Rombout
@mrombout

Ah, so as far as the ispan is concerned all the words are matching, it is not concerned about the extra words in there, that'd be for the qspan. So what is still missing from the key_phrase_filter is checking if key_phrase_span is uninterrupted in the qspan.

If I would use the zip(qspan, ispan) to create a query_key_phrase_span = Span(qpos, qpos + len(key_phrase_span)) if ipos in key_phrase_span to create a Span offset by where it matches. And then check if that is in query_key_phrase_span in qspan. Would that reasoning be in the right direction?

Philippe Ombredanne
@pombredanne
@mrombout hum... let me think a bit... this is a dense question! :D
Mike Rombout
@mrombout
This message was deleted
What I'm trying right now is:
for qpos, ipos in zip(match.qspan, match.ispan):            
    if ipos in key_phrase_span:
        query_key_phrase_span = Span(qpos, qpos + len(key_phrase_span))
        if query_key_phrase_span not in match.qspan:
            has_key_phrases = False
            break
Philippe Ombredanne
@pombredanne
For reference, we have stopwords and unknown words:
  • unknown words DO NOT exist anywhere in any RULE or LICENSE. They can be seen only in the Query.unknowns_by_pos where we only track how many unknown words exist after a known word position. They are not present in the ispan nor the qspan
  • stopwords exist in RULEs and LICENSEs are short, too common words to be useful. They are skipped both on the index and query side. They are not present in the ispan nor the qspan. They can be seen only in the Query.stopwords_by_pos where we only track how many stopwords exist after a known word position.

by construction, key_phrase_span should be :

  • containing no stopwords
  • containing no unknowns

Therefore, it should be possible to do key_phrase_span in match.qspan.
I reckon the code snippet above is for the next step.

Your snippet looks fine to me :+1:
paraphrasing it, I read it this way:
Philippe Ombredanne
@pombredanne
if a matched rule word position is present in a key phrase (i.e. is the first position of a key phrase), then create a query-side span of positions as long as the key phrase, and check if it exists entirely in the matched query
@mrombout is key_phrase_span for a single key phrase or all the key_phrases of a rule?
Mike Rombout
@mrombout

Yes, that's what I was trying to communicate. So that under the {{Creative Commons Attribution 4.0 International License}} (the "License"); won't match under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

The key_phrase_span is a single key phrase.