ruanchaves julien-c HF staff commited on
Commit
e7c0a19
1 Parent(s): 3a9c5f4

Fix `license` metadata (#1)

Browse files

- Fix `license` metadata (d6d61f33d2d9afbca4cbd2b43a57919592a8ed06)


Co-authored-by: Julien Chaumond <[email protected]>

Files changed (1) hide show
  1. README.md +87 -87
README.md CHANGED
@@ -1,88 +1,88 @@
1
- ---
2
- annotations_creators:
3
- - expert-generated
4
- language_creators:
5
- - machine-generated
6
- languages:
7
- - code
8
- licenses:
9
- - unknown
10
- multilinguality:
11
- - monolingual
12
- pretty_name: Binkley
13
- size_categories:
14
- - unknown
15
- source_datasets:
16
- - original
17
- task_categories:
18
- - structure-prediction
19
- task_ids:
20
- - structure-prediction-other-word-segmentation
21
- ---
22
-
23
- # Dataset Card for Binkley
24
-
25
- ## Dataset Description
26
-
27
- - **Paper:** [Normalizing Source Code Vocabulary](https://www.researchgate.net/publication/224198190_Normalizing_Source_Code_Vocabulary)
28
-
29
- ### Dataset Summary
30
-
31
- In programming languages, identifiers are tokens (also called symbols) which name language entities.
32
- Some of the kinds of entities an identifier might denote include variables, types, labels, subroutines, and packages.
33
-
34
- Binkley is a dataset for identifier segmentation, i.e. the task of adding spaces between the words on a identifier.
35
-
36
- ### Languages
37
-
38
- - C
39
- - C++
40
- - Java
41
-
42
- ## Dataset Structure
43
-
44
- ### Data Instances
45
-
46
- ```
47
- {
48
- "index": 0,
49
- "identifier": "init_g16_i",
50
- "segmentation": "init _ g 16 _ i"
51
- }
52
- ```
53
-
54
- ### Data Fields
55
-
56
- - `index`: a numerical index.
57
- - `identifier`: the original identifier.
58
- - `segmentation`: the gold segmentation for the identifier.
59
-
60
- ## Dataset Creation
61
-
62
- - All hashtag segmentation and identifier splitting datasets on this profile have the same basic fields: `hashtag` and `segmentation` or `identifier` and `segmentation`.
63
-
64
- - The only difference between `hashtag` and `segmentation` or between `identifier` and `segmentation` are the whitespace characters. Spell checking, expanding abbreviations or correcting characters to uppercase go into other fields.
65
-
66
- - There is always whitespace between an alphanumeric character and a sequence of any special characters ( such as `_` , `:`, `~` ).
67
-
68
- - If there are any annotations for named entity recognition and other token classification tasks, they are given in a `spans` field.
69
-
70
- ## Additional Information
71
-
72
- ### Citation Information
73
-
74
- ```
75
- @inproceedings{inproceedings,
76
- author = {Lawrie, Dawn and Binkley, David and Morrell, Christopher},
77
- year = {2010},
78
- month = {11},
79
- pages = {3 - 12},
80
- title = {Normalizing Source Code Vocabulary},
81
- journal = {Proceedings - Working Conference on Reverse Engineering, WCRE},
82
- doi = {10.1109/WCRE.2010.10}
83
- }
84
- ```
85
-
86
- ### Contributions
87
-
88
  This dataset was added by [@ruanchaves](https://github.com/ruanchaves) while developing the [hashformers](https://github.com/ruanchaves/hashformers) library.
 
1
+ ---
2
+ annotations_creators:
3
+ - expert-generated
4
+ language_creators:
5
+ - machine-generated
6
+ language:
7
+ - code
8
+ license:
9
+ - unknown
10
+ multilinguality:
11
+ - monolingual
12
+ pretty_name: Binkley
13
+ size_categories:
14
+ - unknown
15
+ source_datasets:
16
+ - original
17
+ task_categories:
18
+ - structure-prediction
19
+ task_ids:
20
+ - structure-prediction-other-word-segmentation
21
+ ---
22
+
23
+ # Dataset Card for Binkley
24
+
25
+ ## Dataset Description
26
+
27
+ - **Paper:** [Normalizing Source Code Vocabulary](https://www.researchgate.net/publication/224198190_Normalizing_Source_Code_Vocabulary)
28
+
29
+ ### Dataset Summary
30
+
31
+ In programming languages, identifiers are tokens (also called symbols) which name language entities.
32
+ Some of the kinds of entities an identifier might denote include variables, types, labels, subroutines, and packages.
33
+
34
+ Binkley is a dataset for identifier segmentation, i.e. the task of adding spaces between the words on a identifier.
35
+
36
+ ### Languages
37
+
38
+ - C
39
+ - C++
40
+ - Java
41
+
42
+ ## Dataset Structure
43
+
44
+ ### Data Instances
45
+
46
+ ```
47
+ {
48
+ "index": 0,
49
+ "identifier": "init_g16_i",
50
+ "segmentation": "init _ g 16 _ i"
51
+ }
52
+ ```
53
+
54
+ ### Data Fields
55
+
56
+ - `index`: a numerical index.
57
+ - `identifier`: the original identifier.
58
+ - `segmentation`: the gold segmentation for the identifier.
59
+
60
+ ## Dataset Creation
61
+
62
+ - All hashtag segmentation and identifier splitting datasets on this profile have the same basic fields: `hashtag` and `segmentation` or `identifier` and `segmentation`.
63
+
64
+ - The only difference between `hashtag` and `segmentation` or between `identifier` and `segmentation` are the whitespace characters. Spell checking, expanding abbreviations or correcting characters to uppercase go into other fields.
65
+
66
+ - There is always whitespace between an alphanumeric character and a sequence of any special characters ( such as `_` , `:`, `~` ).
67
+
68
+ - If there are any annotations for named entity recognition and other token classification tasks, they are given in a `spans` field.
69
+
70
+ ## Additional Information
71
+
72
+ ### Citation Information
73
+
74
+ ```
75
+ @inproceedings{inproceedings,
76
+ author = {Lawrie, Dawn and Binkley, David and Morrell, Christopher},
77
+ year = {2010},
78
+ month = {11},
79
+ pages = {3 - 12},
80
+ title = {Normalizing Source Code Vocabulary},
81
+ journal = {Proceedings - Working Conference on Reverse Engineering, WCRE},
82
+ doi = {10.1109/WCRE.2010.10}
83
+ }
84
+ ```
85
+
86
+ ### Contributions
87
+
88
  This dataset was added by [@ruanchaves](https://github.com/ruanchaves) while developing the [hashformers](https://github.com/ruanchaves/hashformers) library.