upload readme

.idea/LiResolver.iml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<module type="PYTHON_MODULE" version="4">
+  <component name="NewModuleRootManager">
+    <content url="file://$MODULE_DIR$" />
+    <orderEntry type="inheritedJdk" />
+    <orderEntry type="sourceFolder" forTests="false" />
+  </component>
+</module>

.idea/inspectionProfiles/profiles_settings.xml

@@ -0,0 +1,6 @@
+<component name="InspectionProjectProfileManager">
+  <settings>
+    <option name="USE_PROJECT_PROFILE" value="false" />
+    <version value="1.0" />
+  </settings>
+</component>

.idea/modules.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="ProjectModuleManager">
+    <modules>
+      <module fileurl="file://$PROJECT_DIR$/.idea/LiResolver.iml" filepath="$PROJECT_DIR$/.idea/LiResolver.iml" />
+    </modules>
+  </component>
+</project>

EE5/LocateTerms/nermodel/config.py

@@ -57,7 +57,7 @@ class Config():
 
 
     #file_path = "model/LocateTerms/"
-    file_path = "/media/data2/gaoya/OSSL2/EE5/LocateTerms/"
+    file_path = "/xxx/LiResolver/EE5/LocateTerms/"
 
     # general config
     dir_output = file_path+"results/test/"

README.md

@@ -1 +1,29 @@
-# LiResolver
+# LiResolver
+
+
+## Introduction
+Open source software (OSS) licenses regulate the conditions under which OSS can be legally reused, distributed, and modified. However, a common issue arises when incorporating third-party OSS accompanied with licenses, i.e., license incompatibility, which occurs when multiple licenses exist in one project and there are conflicts between them. Despite being problematic, fixing license incompatibility issues requires substantial efforts
+due to the lack of license understanding and complex package dependency.
+In this paper, we propose \tool, a fine-grained, scalable, and flexible tool to resolve license incompatibility issues {for open source software}. Specifically, it first understands the semantics of licenses through fine-grained entity extraction and relation extraction. Then, it detects and resolves license incompatibility issues by recommending official licenses in priority. When no official licenses can satisfy the constraints, it generates a custom license as an alternative solution. Comprehensive experiments demonstrate the effectiveness of \tool, with 4.09\% FP rate and 0.02\% FN rate for incompatibility issue localization, and 62.61\% of 230 real-world incompatible projects resolved by \tool. Furthermore, we also evaluate the impacts of license hierarchy and copyright holder detection on the effectiveness of incompatibility resolution. We discuss lessons learned and made all the datasets and the replication package of \tool publicly available to facilitate follow-up research.
+
+![image](img/overview_00.png)
+
+
+
+## Features
+
+
+
+
+
+## Installation
+
+
+
+
+
+## Example
+
+
+
+