I just had to share this.
A newly added Lexeme Sense L37093#S5 https://www.wikidata.org/wiki/Lexeme:L37093#S5 by me that stemmed from applied research at this URL: https://doi.org/10.1109/TVCG.2017.2744478 that was discovered while playing around with the wonderful Text Visualization Browser https://textvis.lnu.se/ this weekend when I simply searched on "vector" in hopes of seeing some results for anything helping with visualizing Vector Space Models.
Interesting indeed, and also a lovely site, thanks for sharing.
As a side note, I found the use of P5831 novel. I have been taught to put it as a main statement with the qualifier P6072, but your way clearly shows that relation anyway. What are the pros and cons of the two different methods?
Best, Jan Ainali http://ainali.com
Den mån 23 nov. 2020 kl 00:45 skrev Thad Guidry thadguidry@gmail.com:
I just had to share this.
A newly added Lexeme Sense L37093#S5 https://www.wikidata.org/wiki/Lexeme:L37093#S5 by me that stemmed from applied research at this URL: https://doi.org/10.1109/TVCG.2017.2744478 that was discovered while playing around with the wonderful Text Visualization Browser https://textvis.lnu.se/ this weekend when I simply searched on "vector" in hopes of seeing some results for anything helping with visualizing Vector Space Models.
Thad https://www.linkedin.com/in/thadguidry/ _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Pro: The P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 has a constraint (as you can see broken) for only using on the Lexeme main statement, and my way of loosening that constraint actually coincides with the Lexeme Data Model even more...where Senses are where we are allowed to place Synonyms, Translations, etc. to capture the nuances of a Lexeme with many Senses and not limited to only 1 Sense. Allowing P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 at a Sense level to accurately portray the Sense (true meaning). Loosening of the that constraint will be especially important for generic words with 10's to 100's of Senses, and then further see similar usages, even across synonyms. This helps build multilingual knowledge more, not constrained to less. For example: car (en) https://www.wikidata.org/wiki/Lexeme:L3648#2 versus carriage (en-gb) https://www.wikidata.org/wiki/Lexeme:L4759#S2
Con: None
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 1:49 AM Jan Ainali ainali.jan@gmail.com wrote:
Interesting indeed, and also a lovely site, thanks for sharing.
As a side note, I found the use of P5831 novel. I have been taught to put it as a main statement with the qualifier P6072, but your way clearly shows that relation anyway. What are the pros and cons of the two different methods?
Best, Jan Ainali http://ainali.com
Den mån 23 nov. 2020 kl 00:45 skrev Thad Guidry thadguidry@gmail.com:
I just had to share this.
A newly added Lexeme Sense L37093#S5 https://www.wikidata.org/wiki/Lexeme:L37093#S5 by me that stemmed from applied research at this URL: https://doi.org/10.1109/TVCG.2017.2744478 that was discovered while playing around with the wonderful Text Visualization Browser https://textvis.lnu.se/ this weekend when I simply searched on "vector" in hopes of seeing some results for anything helping with visualizing Vector Space Models.
Thad https://www.linkedin.com/in/thadguidry/ _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
But a usage example demonstrates not just a certain sense of a word, but also a certain form. That’s why the usage example statement belongs on the lexeme, not on the sense or form, and links to the relevant sense and form using demonstrates sense (P6072) https://www.wikidata.org/wiki/Property:P6072 and demonstrates form (P5830) https://www.wikidata.org/wiki/Property:P5830. I’ve taken the liberty to rearrange the usage example in that format (link https://www.wikidata.org/wiki/Lexeme:L37093#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5, permalink https://www.wikidata.org/w/index.php?title=Lexeme:L37093&oldid=1312047718#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5).
Cheers, Lucas
PS: I confess I don’t understand what this has to do with Abstract Wikipedia…
On 23.11.20 13:40, Thad Guidry wrote:
Pro: The P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 has a constraint (as you can see broken) for only using on the Lexeme main statement, and my way of loosening that constraint actually coincides with the Lexeme Data Model even more...where Senses are where we are allowed to place Synonyms, Translations, etc. to capture the nuances of a Lexeme with many Senses and not limited to only 1 Sense. Allowing P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 at a Sense level to accurately portray the Sense (true meaning). Loosening of the that constraint will be especially important for generic words with 10's to 100's of Senses, and then further see similar usages, even across synonyms. This helps build multilingual knowledge more, not constrained to less. For example: car (en) https://www.wikidata.org/wiki/Lexeme:L3648#2 versus carriage (en-gb) https://www.wikidata.org/wiki/Lexeme:L4759#S2
Con: None
Thad https://www.linkedin.com/in/thadguidry/ https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 1:49 AM Jan Ainali <ainali.jan@gmail.com mailto:ainali.jan@gmail.com> wrote:
Interesting indeed, and also a lovely site, thanks for sharing. As a side note, I found the use of P5831 novel. I have been taught to put it as a main statement with the qualifier P6072, but your way clearly shows that relation anyway. What are the pros and cons of the two different methods? Best, Jan Ainali http://ainali.com <http://ainali.com> Den mån 23 nov. 2020 kl 00:45 skrev Thad Guidry <thadguidry@gmail.com <mailto:thadguidry@gmail.com>>: I just had to share this. A newly added Lexeme Sense L37093#S5 <https://www.wikidata.org/wiki/Lexeme:L37093#S5> by me that stemmed from applied researchat this URL: https://doi.org/10.1109/TVCG.2017.2744478 <https://doi.org/10.1109/TVCG.2017.2744478>that was discovered while playing around with the wonderful Text Visualization Browser https://textvis.lnu.se/ <https://textvis.lnu.se/> this weekendwhen I simply searched on "vector" in hopes of seeing some results for anything helping with visualizing Vector Space Models. Thad https://www.linkedin.com/in/thadguidry/ <https://www.linkedin.com/in/thadguidry/> _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org <mailto:Abstract-Wikipedia@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia <https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia> _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org <mailto:Abstract-Wikipedia@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia <https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia>
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Ah! demonstrates sense (P6072) https://www.wikidata.org/wiki/Property:P6072 and demonstrates form (P5830) https://www.wikidata.org/wiki/Property:P5830 are alive!
Thanks Lucas! Now I'm off to fix and update some of the Lexicographical documention.
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 3:53 PM Lucas Werkmeister mail@lucaswerkmeister.de wrote:
But a usage example demonstrates not just a certain sense of a word, but also a certain form. That’s why the usage example statement belongs on the lexeme, not on the sense or form, and links to the relevant sense and form using demonstrates sense (P6072) https://www.wikidata.org/wiki/Property:P6072 and demonstrates form (P5830) https://www.wikidata.org/wiki/Property:P5830. I’ve taken the liberty to rearrange the usage example in that format (link https://www.wikidata.org/wiki/Lexeme:L37093#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5, permalink https://www.wikidata.org/w/index.php?title=Lexeme:L37093&oldid=1312047718#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5 ).
Cheers, Lucas
PS: I confess I don’t understand what this has to do with Abstract Wikipedia… On 23.11.20 13:40, Thad Guidry wrote:
Pro: The P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 has a constraint (as you can see broken) for only using on the Lexeme main statement, and my way of loosening that constraint actually coincides with the Lexeme Data Model even more...where Senses are where we are allowed to place Synonyms, Translations, etc. to capture the nuances of a Lexeme with many Senses and not limited to only 1 Sense. Allowing P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 at a Sense level to accurately portray the Sense (true meaning). Loosening of the that constraint will be especially important for generic words with 10's to 100's of Senses, and then further see similar usages, even across synonyms. This helps build multilingual knowledge more, not constrained to less. For example: car (en) https://www.wikidata.org/wiki/Lexeme:L3648#2 versus carriage (en-gb) https://www.wikidata.org/wiki/Lexeme:L4759#S2
Con: None
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 1:49 AM Jan Ainali ainali.jan@gmail.com wrote:
Interesting indeed, and also a lovely site, thanks for sharing.
As a side note, I found the use of P5831 novel. I have been taught to put it as a main statement with the qualifier P6072, but your way clearly shows that relation anyway. What are the pros and cons of the two different methods?
Best, Jan Ainali http://ainali.com
Den mån 23 nov. 2020 kl 00:45 skrev Thad Guidry thadguidry@gmail.com:
I just had to share this.
A newly added Lexeme Sense L37093#S5 https://www.wikidata.org/wiki/Lexeme:L37093#S5 by me that stemmed from applied research at this URL: https://doi.org/10.1109/TVCG.2017.2744478 that was discovered while playing around with the wonderful Text Visualization Browser https://textvis.lnu.se/ this weekend when I simply searched on "vector" in hopes of seeing some results for anything helping with visualizing Vector Space Models.
Thad https://www.linkedin.com/in/thadguidry/ _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing listAbstract-Wikipedia@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Lucas,
Hmm... what to do about the SVG data model that is used on https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation#Da... ? https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation#/m... It shows that 'usage example' goes on statements under Senses (which is where I got my information from, until I hit the constraint issue)
Off-topic concerns with Abstract Wikipedia (yes, I agree with you) - Is there a specific Wikidata mailing list I should be subscribed to additionally to talk specifically about Lexicographical data in Wikidata?
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 4:47 PM Thad Guidry thadguidry@gmail.com wrote:
Ah! demonstrates sense (P6072) https://www.wikidata.org/wiki/Property:P6072 and demonstrates form (P5830) https://www.wikidata.org/wiki/Property:P5830 are alive!
Thanks Lucas! Now I'm off to fix and update some of the Lexicographical documention.
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 3:53 PM Lucas Werkmeister < mail@lucaswerkmeister.de> wrote:
But a usage example demonstrates not just a certain sense of a word, but also a certain form. That’s why the usage example statement belongs on the lexeme, not on the sense or form, and links to the relevant sense and form using demonstrates sense (P6072) https://www.wikidata.org/wiki/Property:P6072 and demonstrates form (P5830) https://www.wikidata.org/wiki/Property:P5830. I’ve taken the liberty to rearrange the usage example in that format (link https://www.wikidata.org/wiki/Lexeme:L37093#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5, permalink https://www.wikidata.org/w/index.php?title=Lexeme:L37093&oldid=1312047718#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5 ).
Cheers, Lucas
PS: I confess I don’t understand what this has to do with Abstract Wikipedia… On 23.11.20 13:40, Thad Guidry wrote:
Pro: The P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 has a constraint (as you can see broken) for only using on the Lexeme main statement, and my way of loosening that constraint actually coincides with the Lexeme Data Model even more...where Senses are where we are allowed to place Synonyms, Translations, etc. to capture the nuances of a Lexeme with many Senses and not limited to only 1 Sense. Allowing P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 at a Sense level to accurately portray the Sense (true meaning). Loosening of the that constraint will be especially important for generic words with 10's to 100's of Senses, and then further see similar usages, even across synonyms. This helps build multilingual knowledge more, not constrained to less. For example: car (en) https://www.wikidata.org/wiki/Lexeme:L3648#2 versus carriage (en-gb) https://www.wikidata.org/wiki/Lexeme:L4759#S2
Con: None
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 1:49 AM Jan Ainali ainali.jan@gmail.com wrote:
Interesting indeed, and also a lovely site, thanks for sharing.
As a side note, I found the use of P5831 novel. I have been taught to put it as a main statement with the qualifier P6072, but your way clearly shows that relation anyway. What are the pros and cons of the two different methods?
Best, Jan Ainali http://ainali.com
Den mån 23 nov. 2020 kl 00:45 skrev Thad Guidry thadguidry@gmail.com:
I just had to share this.
A newly added Lexeme Sense L37093#S5 https://www.wikidata.org/wiki/Lexeme:L37093#S5 by me that stemmed from applied research at this URL: https://doi.org/10.1109/TVCG.2017.2744478 that was discovered while playing around with the wonderful Text Visualization Browser https://textvis.lnu.se/ this weekend when I simply searched on "vector" in hopes of seeing some results for anything helping with visualizing Vector Space Models.
Thad https://www.linkedin.com/in/thadguidry/ _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing listAbstract-Wikipedia@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
I have corrected the svg now (it may take a while for png thumbnails to update).
Best, Jan Ainali
Den tis 24 nov. 2020 kl 00:34 skrev Thad Guidry thadguidry@gmail.com:
Lucas,
Hmm... what to do about the SVG data model that is used on https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation#Da... ?
https://www.wikidata.org/wiki/Wikidata:Lexicographical_data/Documentation#/m... It shows that 'usage example' goes on statements under Senses (which is where I got my information from, until I hit the constraint issue)
Off-topic concerns with Abstract Wikipedia (yes, I agree with you) - Is there a specific Wikidata mailing list I should be subscribed to additionally to talk specifically about Lexicographical data in Wikidata?
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 4:47 PM Thad Guidry thadguidry@gmail.com wrote:
Ah! demonstrates sense (P6072) https://www.wikidata.org/wiki/Property:P6072 and demonstrates form (P5830) https://www.wikidata.org/wiki/Property:P5830 are alive!
Thanks Lucas! Now I'm off to fix and update some of the Lexicographical documention.
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 3:53 PM Lucas Werkmeister < mail@lucaswerkmeister.de> wrote:
But a usage example demonstrates not just a certain sense of a word, but also a certain form. That’s why the usage example statement belongs on the lexeme, not on the sense or form, and links to the relevant sense and form using demonstrates sense (P6072) https://www.wikidata.org/wiki/Property:P6072 and demonstrates form (P5830) https://www.wikidata.org/wiki/Property:P5830. I’ve taken the liberty to rearrange the usage example in that format (link https://www.wikidata.org/wiki/Lexeme:L37093#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5, permalink https://www.wikidata.org/w/index.php?title=Lexeme:L37093&oldid=1312047718#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5 ).
Cheers, Lucas
PS: I confess I don’t understand what this has to do with Abstract Wikipedia… On 23.11.20 13:40, Thad Guidry wrote:
Pro: The P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 has a constraint (as you can see broken) for only using on the Lexeme main statement, and my way of loosening that constraint actually coincides with the Lexeme Data Model even more...where Senses are where we are allowed to place Synonyms, Translations, etc. to capture the nuances of a Lexeme with many Senses and not limited to only 1 Sense. Allowing P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 at a Sense level to accurately portray the Sense (true meaning). Loosening of the that constraint will be especially important for generic words with 10's to 100's of Senses, and then further see similar usages, even across synonyms. This helps build multilingual knowledge more, not constrained to less. For example: car (en) https://www.wikidata.org/wiki/Lexeme:L3648#2 versus carriage (en-gb) https://www.wikidata.org/wiki/Lexeme:L4759#S2
Con: None
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 1:49 AM Jan Ainali ainali.jan@gmail.com wrote:
Interesting indeed, and also a lovely site, thanks for sharing.
As a side note, I found the use of P5831 novel. I have been taught to put it as a main statement with the qualifier P6072, but your way clearly shows that relation anyway. What are the pros and cons of the two different methods?
Best, Jan Ainali http://ainali.com
Den mån 23 nov. 2020 kl 00:45 skrev Thad Guidry thadguidry@gmail.com:
I just had to share this.
A newly added Lexeme Sense L37093#S5 https://www.wikidata.org/wiki/Lexeme:L37093#S5 by me that stemmed from applied research at this URL: https://doi.org/10.1109/TVCG.2017.2744478 that was discovered while playing around with the wonderful Text Visualization Browser https://textvis.lnu.se/ this weekend when I simply searched on "vector" in hopes of seeing some results for anything helping with visualizing Vector Space Models.
Thad https://www.linkedin.com/in/thadguidry/ _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing listAbstract-Wikipedia@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
This is folksonomy at its best (and worst, depending on how you look)!
On Mon, 23 Nov 2020, 21:53 Lucas Werkmeister, mail@lucaswerkmeister.de wrote:
But a usage example demonstrates not just a certain sense of a word, but also a certain form. That’s why the usage example statement belongs on the lexeme, not on the sense or form, and links to the relevant sense and form using demonstrates sense (P6072) https://www.wikidata.org/wiki/Property:P6072 and demonstrates form (P5830) https://www.wikidata.org/wiki/Property:P5830. I’ve taken the liberty to rearrange the usage example in that format (link https://www.wikidata.org/wiki/Lexeme:L37093#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5, permalink https://www.wikidata.org/w/index.php?title=Lexeme:L37093&oldid=1312047718#L37093$c87964da-4e77-a37b-2bfd-396b4cc3b5d5 ).
Cheers, Lucas
PS: I confess I don’t understand what this has to do with Abstract Wikipedia… On 23.11.20 13:40, Thad Guidry wrote:
Pro: The P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 has a constraint (as you can see broken) for only using on the Lexeme main statement, and my way of loosening that constraint actually coincides with the Lexeme Data Model even more...where Senses are where we are allowed to place Synonyms, Translations, etc. to capture the nuances of a Lexeme with many Senses and not limited to only 1 Sense. Allowing P5831 "usage example" https://www.wikidata.org/wiki/Property:P5831 at a Sense level to accurately portray the Sense (true meaning). Loosening of the that constraint will be especially important for generic words with 10's to 100's of Senses, and then further see similar usages, even across synonyms. This helps build multilingual knowledge more, not constrained to less. For example: car (en) https://www.wikidata.org/wiki/Lexeme:L3648#2 versus carriage (en-gb) https://www.wikidata.org/wiki/Lexeme:L4759#S2
Con: None
Thad https://www.linkedin.com/in/thadguidry/
On Mon, Nov 23, 2020 at 1:49 AM Jan Ainali ainali.jan@gmail.com wrote:
Interesting indeed, and also a lovely site, thanks for sharing.
As a side note, I found the use of P5831 novel. I have been taught to put it as a main statement with the qualifier P6072, but your way clearly shows that relation anyway. What are the pros and cons of the two different methods?
Best, Jan Ainali http://ainali.com
Den mån 23 nov. 2020 kl 00:45 skrev Thad Guidry thadguidry@gmail.com:
I just had to share this.
A newly added Lexeme Sense L37093#S5 https://www.wikidata.org/wiki/Lexeme:L37093#S5 by me that stemmed from applied research at this URL: https://doi.org/10.1109/TVCG.2017.2744478 that was discovered while playing around with the wonderful Text Visualization Browser https://textvis.lnu.se/ this weekend when I simply searched on "vector" in hopes of seeing some results for anything helping with visualizing Vector Space Models.
Thad https://www.linkedin.com/in/thadguidry/ _______________________________________________ Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing listAbstract-Wikipedia@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
Abstract-Wikipedia mailing list Abstract-Wikipedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/abstract-wikipedia
abstract-wikipedia@lists.wikimedia.org