Re: [SMW-devel] Semantic Parser Engine
23.04.2010 23:41, Jeff Thompson ?: If Wikipedia will only have the data but no query (because it's a burden for its servers), then maybe there should be software on the client to download the raw data and process the query locally. In some browsers, even javascript is fast enough for this, so that the browser can fill in the section of the page showing the query result. Has there been any thought along these lines. Of course. One may import such dump into his wiki (assuming the hardware is powerful enough) to use full-featured version of SMW to query these data privately or with much limited amount of users than Wikipedia has. Dmitriy -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Semantic Parser Engine
22.04.2010 18:04, Jeroen De Dauw пишет: Hey, How likely will Wikipedia adopt SMW some time in the future? This won't be any time soon. There is some effort going on to get a stripped down version of SMW that does not have query capabilities onto commons though. Getting SMW on other WMF wiki's will depend a lot on the outcome of this. How would they want to achieve that? Does SMW currently have some kind of miser mode similar to MW's miser mode? Dmitriy -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Semantic Parser Engine
How would they want to achieve that? Does SMW currently have some kind of miser mode similar to MW's miser mode? SMW does currently not have the ability to have only the storage infrastructure. Markus is planning on making it modular in a way that this will be possible though. The main reason for this is to shrink the codebase to something that can be reviewed by some WMF people, which is a requirement to getting it onto any WMF wiki. -- Jeroen De Dauw * http://blog.bn2vs.com * http://wiki.bn2vs.com Don't panic. Don't be evil. 70 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65! -- -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Semantic Parser Engine
Okay, wow. :) Indeed, there's no way to do this kind of querying (to the extent that I can even understand it) using regular SMW. But, in lieu of writing a lot of new code: have you considered accessing the SMW data as RDF? There are a whole set of tools for doing complex queries on RDF data, and there are even some tools that let you run SPARQL queries on a wiki's data from directly within the wiki. See here for an explanation of how to export SMW data to RDF: http://semantic-mediawiki.org/wiki/Help:RDF_export -Yaron On Thu, Apr 22, 2010 at 8:55 PM, Nathanael Thompson than4...@gmail.comwrote: Here's 2: Note, these use cases happen in a perfect (less exciting) world. Seemless parsing experience based on semantic info put in place by someone else: Someone else previously specified that: - UCAG are common tags for nucleic acids - what amino acids result from what nucleic acids triplets - what triplets are used to start and stop the encoding a protein - what amino acid sequences make up each protein Another person has a long sequence of nucleic acid values and wants to know what proteins it would produce. She specifies that she is inputting a nucleic acid sequence and that she wants proteins outputted. The parser uses the combination of tag info and the info about how to get proteins from nucleic acid sequences to seemlessly provide the scientist with the proteins she desires. Gaining semantic info from a grammar that can be used in non parser task: A person writes a grammar for encoding family tree info using ebnf. This grammar includes the following lines: Person = [Spouse], Mother, Father, {Child}; Spouse = Spouse: , Name; He just enters the ebnf into the wiki because someone else already specified how to parse ebnf. From this text the wiki stores the fact that with this grammar Spouse: specifies that the name of a spouse is coming. Also, the parser stores that a person has 0 or 1 spouses, exactly one mother and father and any number of children (All valuable ontology info that can be used elsewhere). After inputting the grammar the person thinks to him self: parser info seems a lot like ontology info plus tag info. Elsewhere ... Droid asks the wiki how many mothers a person has and it answers exactly 2. I'm fine making an extension for this. Nate On Thu, Apr 22, 2010 at 9:57 AM, Yaron Koren yaro...@gmail.com wrote: Nathanael - could you present a use case or two for the kind of querying you're talking about? -Yaron On Thu, Apr 22, 2010 at 10:04 AM, Jeroen De Dauw jeroended...@gmail.comwrote: Hey, How likely will Wikipedia adopt SMW some time in the future? This won't be any time soon. There is some effort going on to get a stripped down version of SMW that does not have query capabilities onto commons though. Getting SMW on other WMF wiki's will depend a lot on the outcome of this. Would it be best for me to develop this in the main SMW source code, a branch, or an extension? An extension, as we do not want to add any more code to SMW core. Cheers -- Jeroen De Dauw * http://blog.bn2vs.com * http://wiki.bn2vs.com Don't panic. Don't be evil. 70 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65! -- On 22 April 2010 07:19, Nathanael Thompson than4...@gmail.com wrote: Hello All, I'm interested in adding a feature to Semantic MediaWiki, and I'd like to hear what the community thinks about it. But first, I was wondering: How likely will Wikipedia adopt SMW some time in the future? I'm interested in creating a parser that uses ontologies to help with parsing. For example, a functional property might be used like a regular expression ? and no upper cardinality restriction could be used like a regular expression *. Also, tag info could be used to help the parser know which property to use next while parsing. Of course, the implementation would be much more complicated than I can describe in an email. I think this type of parser would be useful because it will allow people who have a bunch of data in text format to easily set up the grammar for the data and integrate it into the SMW database. How well would this mesh with the rest of the work going on in SMW? Would it be best for me to develop this in the main SMW source code, a branch, or an extension? Is there anybody else who would like to collaborate with this project? Any other questions or comments would be appreciated. Nate -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net
Re: [SMW-devel] Semantic Parser Engine
If Wikipedia will only have the data but no query (because it's a burden for its servers), then maybe there should be software on the client to download the raw data and process the query locally. In some browsers, even javascript is fast enough for this, so that the browser can fill in the section of the page showing the query result. Has there been any thought along these lines. The stripped down version with no query capabilities is intended for Commons, not Wikipedia. Like stated, currently the main issue is the size of the SMW codebase, not necessary it's performance. -- Jeroen De Dauw * http://blog.bn2vs.com * http://wiki.bn2vs.com Don't panic. Don't be evil. 70 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65! -- -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Semantic Parser Engine
If Wikipedia will only have the data but no query (because it's a burden for its servers), then maybe there should be software on the client to download the raw data and process the query locally. In some browsers, even javascript is fast enough for this, so that the browser can fill in the section of the page showing the query result. Has there been any thought along these lines. On 4/23/2010 6:07 AM, Jeroen De Dauw wrote: How would they want to achieve that? Does SMW currently have some kind of miser mode similar to MW's miser mode? SMW does currently not have the ability to have only the storage infrastructure. Markus is planning on making it modular in a way that this will be possible though. The main reason for this is to shrink the codebase to something that can be reviewed by some WMF people, which is a requirement to getting it onto any WMF wiki. -- Jeroen De Dauw * http://blog.bn2vs.com * http://wiki.bn2vs.com Don't panic. Don't be evil. 70 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65! -- -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Semantic Parser Engine
Hey, How likely will Wikipedia adopt SMW some time in the future? This won't be any time soon. There is some effort going on to get a stripped down version of SMW that does not have query capabilities onto commons though. Getting SMW on other WMF wiki's will depend a lot on the outcome of this. Would it be best for me to develop this in the main SMW source code, a branch, or an extension? An extension, as we do not want to add any more code to SMW core. Cheers -- Jeroen De Dauw * http://blog.bn2vs.com * http://wiki.bn2vs.com Don't panic. Don't be evil. 70 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65! -- On 22 April 2010 07:19, Nathanael Thompson than4...@gmail.com wrote: Hello All, I'm interested in adding a feature to Semantic MediaWiki, and I'd like to hear what the community thinks about it. But first, I was wondering: How likely will Wikipedia adopt SMW some time in the future? I'm interested in creating a parser that uses ontologies to help with parsing. For example, a functional property might be used like a regular expression ? and no upper cardinality restriction could be used like a regular expression *. Also, tag info could be used to help the parser know which property to use next while parsing. Of course, the implementation would be much more complicated than I can describe in an email. I think this type of parser would be useful because it will allow people who have a bunch of data in text format to easily set up the grammar for the data and integrate it into the SMW database. How well would this mesh with the rest of the work going on in SMW? Would it be best for me to develop this in the main SMW source code, a branch, or an extension? Is there anybody else who would like to collaborate with this project? Any other questions or comments would be appreciated. Nate -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
Re: [SMW-devel] Semantic Parser Engine
Here's 2: Note, these use cases happen in a perfect (less exciting) world. Seemless parsing experience based on semantic info put in place by someone else: Someone else previously specified that: - UCAG are common tags for nucleic acids - what amino acids result from what nucleic acids triplets - what triplets are used to start and stop the encoding a protein - what amino acid sequences make up each protein Another person has a long sequence of nucleic acid values and wants to know what proteins it would produce. She specifies that she is inputting a nucleic acid sequence and that she wants proteins outputted. The parser uses the combination of tag info and the info about how to get proteins from nucleic acid sequences to seemlessly provide the scientist with the proteins she desires. Gaining semantic info from a grammar that can be used in non parser task: A person writes a grammar for encoding family tree info using ebnf. This grammar includes the following lines: Person = [Spouse], Mother, Father, {Child}; Spouse = Spouse: , Name; He just enters the ebnf into the wiki because someone else already specified how to parse ebnf. From this text the wiki stores the fact that with this grammar Spouse: specifies that the name of a spouse is coming. Also, the parser stores that a person has 0 or 1 spouses, exactly one mother and father and any number of children (All valuable ontology info that can be used elsewhere). After inputting the grammar the person thinks to him self: parser info seems a lot like ontology info plus tag info. Elsewhere ... Droid asks the wiki how many mothers a person has and it answers exactly 2. I'm fine making an extension for this. Nate On Thu, Apr 22, 2010 at 9:57 AM, Yaron Koren yaro...@gmail.com wrote: Nathanael - could you present a use case or two for the kind of querying you're talking about? -Yaron On Thu, Apr 22, 2010 at 10:04 AM, Jeroen De Dauw jeroended...@gmail.comwrote: Hey, How likely will Wikipedia adopt SMW some time in the future? This won't be any time soon. There is some effort going on to get a stripped down version of SMW that does not have query capabilities onto commons though. Getting SMW on other WMF wiki's will depend a lot on the outcome of this. Would it be best for me to develop this in the main SMW source code, a branch, or an extension? An extension, as we do not want to add any more code to SMW core. Cheers -- Jeroen De Dauw * http://blog.bn2vs.com * http://wiki.bn2vs.com Don't panic. Don't be evil. 70 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65! -- On 22 April 2010 07:19, Nathanael Thompson than4...@gmail.com wrote: Hello All, I'm interested in adding a feature to Semantic MediaWiki, and I'd like to hear what the community thinks about it. But first, I was wondering: How likely will Wikipedia adopt SMW some time in the future? I'm interested in creating a parser that uses ontologies to help with parsing. For example, a functional property might be used like a regular expression ? and no upper cardinality restriction could be used like a regular expression *. Also, tag info could be used to help the parser know which property to use next while parsing. Of course, the implementation would be much more complicated than I can describe in an email. I think this type of parser would be useful because it will allow people who have a bunch of data in text format to easily set up the grammar for the data and integrate it into the SMW database. How well would this mesh with the rest of the work going on in SMW? Would it be best for me to develop this in the main SMW source code, a branch, or an extension? Is there anybody else who would like to collaborate with this project? Any other questions or comments would be appreciated. Nate -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel -- WikiWorks · MediaWiki Consulting · http://wikiworks.com -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel -- ___ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel