From 1a2542fde2bf6feea93817fef8a9c6062857c15b Mon Sep 17 00:00:00 2001 From: Pradeep Kumar Tippa Date: Wed, 7 Feb 2018 15:41:24 +0530 Subject: [PATCH 1/4] Merge from Patch 1 (#1) * Fixing vocab doc Replacing "like" with "love", coffee suffix should be "fee" but not "ffe" * Added pktippa contributor agreement --- .github/contributors/pktippa.md | 106 +++++++++++++++++++++++++++ website/usage/_spacy-101/_vocab.jade | 4 +- 2 files changed, 108 insertions(+), 2 deletions(-) create mode 100644 .github/contributors/pktippa.md diff --git a/.github/contributors/pktippa.md b/.github/contributors/pktippa.md new file mode 100644 index 000000000..740944a72 --- /dev/null +++ b/.github/contributors/pktippa.md @@ -0,0 +1,106 @@ +# spaCy contributor agreement + +This spaCy Contributor Agreement (**"SCA"**) is based on the +[Oracle Contributor Agreement](http://www.oracle.com/technetwork/oca-405177.pdf). +The SCA applies to any contribution that you make to any product or project +managed by us (the **"project"**), and sets out the intellectual property rights +you grant to us in the contributed materials. The term **"us"** shall mean +[ExplosionAI UG (haftungsbeschränkt)](https://explosion.ai/legal). The term +**"you"** shall mean the person or entity identified below. + +If you agree to be bound by these terms, fill in the information requested +below and include the filled-in version with your first pull request, under the +folder [`.github/contributors/`](/.github/contributors/). The name of the file +should be your GitHub username, with the extension `.md`. For example, the user +example_user would create the file `.github/contributors/example_user.md`. + +Read this agreement carefully before signing. These terms and conditions +constitute a binding legal agreement. + +## Contributor Agreement + +1. The term "contribution" or "contributed materials" means any source code, +object code, patch, tool, sample, graphic, specification, manual, +documentation, or any other material posted or submitted by you to the project. + +2. With respect to any worldwide copyrights, or copyright applications and +registrations, in your contribution: + + * you hereby assign to us joint ownership, and to the extent that such + assignment is or becomes invalid, ineffective or unenforceable, you hereby + grant to us a perpetual, irrevocable, non-exclusive, worldwide, no-charge, + royalty-free, unrestricted license to exercise all rights under those + copyrights. This includes, at our option, the right to sublicense these same + rights to third parties through multiple levels of sublicensees or other + licensing arrangements; + + * you agree that each of us can do all things in relation to your + contribution as if each of us were the sole owners, and if one of us makes + a derivative work of your contribution, the one who makes the derivative + work (or has it made will be the sole owner of that derivative work; + + * you agree that you will not assert any moral rights in your contribution + against us, our licensees or transferees; + + * you agree that we may register a copyright in your contribution and + exercise all ownership rights associated with it; and + + * you agree that neither of us has any duty to consult with, obtain the + consent of, pay or render an accounting to the other for any use or + distribution of your contribution. + +3. With respect to any patents you own, or that you can license without payment +to any third party, you hereby grant to us a perpetual, irrevocable, +non-exclusive, worldwide, no-charge, royalty-free license to: + + * make, have made, use, sell, offer to sell, import, and otherwise transfer + your contribution in whole or in part, alone or in combination with or + included in any product, work or materials arising out of the project to + which your contribution was submitted, and + + * at our option, to sublicense these same rights to third parties through + multiple levels of sublicensees or other licensing arrangements. + +4. Except as set out above, you keep all right, title, and interest in your +contribution. The rights that you grant to us under these terms are effective +on the date you first submitted a contribution to us, even if your submission +took place before the date you sign these terms. + +5. You covenant, represent, warrant and agree that: + + * Each contribution that you submit is and shall be an original work of + authorship and you can legally grant the rights set out in this SCA; + + * to the best of your knowledge, each contribution will not violate any + third party's copyrights, trademarks, patents, or other intellectual + property rights; and + + * each contribution shall be in compliance with U.S. export control laws and + other applicable export and import laws. You agree to notify us if you + become aware of any circumstance which would make any of the foregoing + representations inaccurate in any respect. We may publicly disclose your + participation in the project, including the fact that you have signed the SCA. + +6. This SCA is governed by the laws of the State of California and applicable +U.S. Federal law. Any choice of law rules will not apply. + +7. Please place an “x” on one of the applicable statement below. Please do NOT +mark both statements: + + * [x] I am signing on behalf of myself as an individual and no other person + or entity, including my employer, has or will have rights with respect to my + contributions. + + * [x] I am signing on behalf of my employer or a legal entity and I have the + actual authority to contractually bind that entity. + +## Contributor Details + +| Field | Entry | +|------------------------------- | -------------------- | +| Name | Pradeep Kumar Tippa | +| Company name (if applicable) | | +| Title or role (if applicable) | | +| Date | 07-02-2018 | +| GitHub username | pktippa | +| Website (optional) | | diff --git a/website/usage/_spacy-101/_vocab.jade b/website/usage/_spacy-101/_vocab.jade index 185e634fe..b81e0f33c 100644 --- a/website/usage/_spacy-101/_vocab.jade +++ b/website/usage/_spacy-101/_vocab.jade @@ -32,7 +32,7 @@ p | string to get its hash, or a hash to get its string: +code. - doc = nlp(u'I like coffee') + doc = nlp(u'I love coffee') assert doc.vocab.strings[u'coffee'] == 3197928453018144401 assert doc.vocab.strings[3197928453018144401] == u'coffee' @@ -70,7 +70,7 @@ p - var style = [0, 1, 1, 0, 0, 1, 1] +annotation-row(["I", "4690420944186131903", "X", "I", "I", true, false], style) +annotation-row(["love", "3702023516439754181", "xxxx", "l", "ove", true, false], style) - +annotation-row(["coffee", "3197928453018144401", "xxxx", "c", "ffe", true, false], style) + +annotation-row(["coffee", "3197928453018144401", "xxxx", "c", "fee", true, false], style) p | The mapping of words to hashes doesn't depend on any state. To make sure From 03113d67799efd2999edf85ac98f7261ae7ecb48 Mon Sep 17 00:00:00 2001 From: Pradeep Kumar Tippa Date: Thu, 8 Feb 2018 19:34:15 +0530 Subject: [PATCH 2/4] Fixing navigating parse tree doc under dependency parse --- website/usage/_linguistic-features/_dependency-parse.jade | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/usage/_linguistic-features/_dependency-parse.jade b/website/usage/_linguistic-features/_dependency-parse.jade index 188b7b8f3..d8d7cbce1 100644 --- a/website/usage/_linguistic-features/_dependency-parse.jade +++ b/website/usage/_linguistic-features/_dependency-parse.jade @@ -65,9 +65,9 @@ p - var style = [0, 1, 0, 1, 0] +annotation-row(["Autonomous", "amod", "cars", "NOUN", ""], style) +annotation-row(["cars", "nsubj", "shift", "VERB", "Autonomous"], style) - +annotation-row(["shift", "ROOT", "shift", "VERB", "cars, liability"], style) + +annotation-row(["shift", "ROOT", "shift", "VERB", "cars, liability, toward"], style) +annotation-row(["insurance", "compound", "liability", "NOUN", ""], style) - +annotation-row(["liability", "dobj", "shift", "VERB", "insurance, toward"], style) + +annotation-row(["liability", "dobj", "shift", "VERB", "insurance"], style) +annotation-row(["toward", "prep", "liability", "NOUN", "manufacturers"], style) +annotation-row(["manufacturers", "pobj", "toward", "ADP", ""], style) From 01cc9cd9c03c050756679a4f457b98f0dc6c30bc Mon Sep 17 00:00:00 2001 From: Pradeep Kumar Tippa Date: Fri, 9 Feb 2018 19:16:25 +0530 Subject: [PATCH 3/4] assert statement syntax fix in doc --- website/usage/_linguistic-features/_named-entities.jade | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/usage/_linguistic-features/_named-entities.jade b/website/usage/_linguistic-features/_named-entities.jade index 9e55ba84e..0f32d1da3 100644 --- a/website/usage/_linguistic-features/_named-entities.jade +++ b/website/usage/_linguistic-features/_named-entities.jade @@ -80,7 +80,7 @@ p doc.ents = [netflix_ent] ents = [(e.text, e.start_char, e.end_char, e.label_) for e in doc.ents] - assert ents = [(u'Netflix', 0, 7, u'ORG')] + assert ents == [(u'Netflix', 0, 7, u'ORG')] p | Keep in mind that you need to create a #[code Span] with the start and From 416cd021cee39a9a61045c6438518f6eb137723a Mon Sep 17 00:00:00 2001 From: Pradeep Kumar Tippa Date: Fri, 9 Feb 2018 19:16:59 +0530 Subject: [PATCH 4/4] Added TAG from spacy symbols which used below --- website/usage/_linguistic-features/_tokenization.jade | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/usage/_linguistic-features/_tokenization.jade b/website/usage/_linguistic-features/_tokenization.jade index f149556ce..2cd3a13de 100644 --- a/website/usage/_linguistic-features/_tokenization.jade +++ b/website/usage/_linguistic-features/_tokenization.jade @@ -54,7 +54,7 @@ p +code. import spacy - from spacy.symbols import ORTH, LEMMA, POS + from spacy.symbols import ORTH, LEMMA, POS, TAG nlp = spacy.load('en') doc = nlp(u'gimme that') # phrase to tokenize