• Reference Mark extra-phrase position in rules #4515
• This will be merged after Improve score by supporting extra_phrase for extra words in rules #4432

In this PR, I added extra-phrase maker in rules. I am doing by license-expression wise. First i am doing for bsd-new license_expression.

Introducing new repo: (What they do?) named-entity-utils

Named-Entity Removal:

• Automatically removes named-entities (e.g., PERSON, ORG, GPE) from license rules.
• Users can provide a specific license-expression, ensuring that named-entity removal is applied only to those rules.

Duplicate Rule Detection:

• After named-entity removal, we can also detect and output duplicate rules.
• Results are provided in JSON format, making it clear which rule files match each other after removing named-entity.

A detailed README is included with instructions on how to set up and run the tool.

Processing Steps for BSD-New(eg) Rules

1. Remove all named-entities from BSD-New rules using named-entity-utils.
2. Detect duplicate rules (after named-entity removal) and export them in JSON format.
3. For each group of duplicate rules:
   • If a rule already exists without a named-entity at the target position, add an extra-phrase marker there.
   • If no such rule exists, create a new rule with an extra-phrase marker at the position named-entity.
4. Handle edge cases:
   • If a removed named-entity is not actually a named-entity, then do not modify that rule (no new rule, no extra-phrase).
   • This ensures we only adjust rules where named-entities truly exist.

For bsd-new license we got these duplicate rules after removing named-entity from all rules of bsd-new license.
File:
bsd-new_duplicates_rules.json

Tasks

• Reviewed contribution guidelines
• PR is descriptively titled 📑 and links the original issue above 🔗
• Tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR
  Run tests locally to check for errors.
• Commits are in uniquely-named feature branch and has no merge conflicts 📁
• Updated documentation pages (if applicable)
• Updated CHANGELOG.rst (if applicable)

Signed-off-by: Alok Kumar [email protected]