From: David E. <dav...@um...> - 2010-10-19 16:49:34
|
Hi everyone, I would like to use semantic media wiki to formalize the knowledge in journal articles and to compare statements made between the articles. For me, this involves organizing what the articles say about various "cases". I'd like to improve on my current method of doing this and am hoping for suggestions from more advanced users. Right now, after a particularly informative paragraph in an article, I code some of the information using #set_internal. But this has a few drawbacks: 1. All the properties for a particular set_internal instance or "case", need to be coded at once, even if the actual material is spread throughout the article--even throughout multiple articles. I would like to be able to code as I read the article, adding to various cases as I see relevant new information. It is important to keep in mind that (A) sometimes elements related to a case may be spread across several articles, and (B) if a case's property is set more than once, then both values should be stored and displayed in a query. 2. Using my current method, the #set_internal instances when queried show as a matrix of mostly red-links to new pages. Often, I would prefer if the links jumped back to the point in the original article where I set the property. 3. Perhaps another way to explain the result would be a page of properties for each case. Some properties would have multiple values assigned. Clicking on a value would take me to the place in an article where I assigned that value to that case and property. Here is an example of what I am currently doing: {{#set_internal:IsPartDiff |HasTopic=Case |HasVersion#list=Community informatics, Disinvestment, Slum housing, Neighborhood Knowledge Los Angeles (NKLA) |HasLocation=Los Angeles |HasStartDate=1996 }} {{#set_internal:IsPartDiff |HasTopic=Case |HasVersion#list=Neighborhood Early Warning System |HasLocation=Chicago }} Comments and/or suggestions would be appreciated thank you, -david |
From: Jesse W. <wj...@gm...> - 2010-10-19 18:11:41
|
Hi, David - What you need achieve is quite reasonable. #sen_internal is a great helper yet it still has limitations. I believe for your case, the best way to achieve is through a semantic storage backend, that is to say, a triple store with provenance support (source tracking). Ontoprise currently provides commercial solutions for this type of problems (go to http://wiki.ontoprise.com/, look for Halo suite of extensions and more, such as Triple Store connector, Linked Data extension, etc.) to learn more. You probably can get away with a low cost installation package if you know how to DIY. Otherwise, I believe they are more than happy to provide professional grade consulting and enterprise solutions for you. Best regards, Jesse On Tue, Oct 19, 2010 at 9:49 AM, David Epstein <dav...@um...> wrote: > Hi everyone, > > > I would like to use semantic media wiki to formalize the knowledge in > journal articles and to compare statements made between the articles. > For me, this involves organizing what the articles say about various > "cases". > > I'd like to improve on my current method of doing this and am hoping for > suggestions from more advanced users. Right now, after a particularly > informative paragraph in an article, I code some of the information > using #set_internal. But this has a few drawbacks: > > 1. All the properties for a particular set_internal instance or "case", > need to be coded at once, even if the actual material is spread > throughout the article--even throughout multiple articles. I would like > to be able to code as I read the article, adding to various cases as I > see relevant new information. It is important to keep in mind that (A) > sometimes elements related to a case may be spread across several > articles, and (B) if a case's property is set more than once, then both > values should be stored and displayed in a query. > > 2. Using my current method, the #set_internal instances when queried > show as a matrix of mostly red-links to new pages. Often, I would prefer > if the links jumped back to the point in the original article where I > set the property. > > 3. Perhaps another way to explain the result would be a page of > properties for each case. Some properties would have multiple values > assigned. Clicking on a value would take me to the place in an article > where I assigned that value to that case and property. > > Here is an example of what I am currently doing: > > {{#set_internal:IsPartDiff > |HasTopic=Case > |HasVersion#list=Community informatics, Disinvestment, Slum housing, > Neighborhood Knowledge Los Angeles (NKLA) > |HasLocation=Los Angeles > |HasStartDate=1996 > }} > > {{#set_internal:IsPartDiff > |HasTopic=Case > |HasVersion#list=Neighborhood Early Warning System > |HasLocation=Chicago > }} > > Comments and/or suggestions would be appreciated > > > thank you, > -david > > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > |
From: David E. <dav...@um...> - 2010-10-19 18:47:48
|
Hi Jesse Thank you for your reply. I'm a doctoral student and this is related to my personal research and projects. I will not be able to afford a commercial solution. Are there opensource solutions, like sesame or allegrograph? Is there a parser hook of some kind to insert the data into the store? The Tetherless_Map extension looks like it is specifically for geographic maps. So, that may not work. -david |
From: Laurent A. <la...@al...> - 2010-10-19 18:56:32
|
A review of open sources alternatives is available here : http://www.mediawiki.org/wiki/Extension:SparqlExtension - Laurent On Oct 19, 2010, at 2:38 PM, David Epstein wrote: > Hi Jesse > > Thank you for your reply. > > I'm a doctoral student and this is related to my personal research and > projects. I will not be able to afford a commercial solution. Are there > opensource solutions, like sesame or allegrograph? Is there a parser > hook of some kind to insert the data into the store? > > The Tetherless_Map extension looks like it is specifically for > geographic maps. So, that may not work. > > -david > > > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user |
From: Laurent A. <la...@al...> - 2010-10-19 19:00:07
|
A more detailed review and ongoing discussion of options for Triple Store support in SMW is available here : http://semantic-mediawiki.org/wiki/SPARQL_and_RDF_stores_for_SMW And here is the documentation for the default option for Triple store using RAP: http://semantic-mediawiki.org/wiki/Help:SPARQL_endpoint - Laurent On Oct 19, 2010, at 2:38 PM, David Epstein wrote: > Hi Jesse > > Thank you for your reply. > > I'm a doctoral student and this is related to my personal research and > projects. I will not be able to afford a commercial solution. Are there > opensource solutions, like sesame or allegrograph? Is there a parser > hook of some kind to insert the data into the store? > > The Tetherless_Map extension looks like it is specifically for > geographic maps. So, that may not work. > > -david > > > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user |
From: Yaron K. <ya...@gm...> - 2010-10-19 19:27:30
|
Hi, I don't see the connection between the original question and triple stores; but I must be missing something, because now that's the subject of this whole thread. Isn't this just a question about data organization, as opposed to data storage on the back-end? In any case, my recommendation for the original question would be to store the data in separate pages from the articles themselves. It's neat to be able to annotate the articles inline, but, as you've discovered, you lose some flexibility, including the ability to refer to multiple articles at once. I don't quite understand your data structure, including what a "case" is, but I would recommend having pages specifically for the data, created and edited using Semantic Forms, where you either have one page for each "case" (I guess), or have multiple "cases" per page, using multiple-instance templates and #set_internal. Using templates and forms will provide more structure and a nicer display, and I think it'll save you time in the long run. And you can link back to the original article section using a property of type "URL" (the "Page" type doesn't allow linking to a subsection of a page). -Yaron On Tue, Oct 19, 2010 at 2:59 PM, Laurent Alquier <la...@al...> wrote: > A more detailed review and ongoing discussion of options for Triple Store support in SMW is available here : > > http://semantic-mediawiki.org/wiki/SPARQL_and_RDF_stores_for_SMW > > And here is the documentation for the default option for Triple store using RAP: > > http://semantic-mediawiki.org/wiki/Help:SPARQL_endpoint > > - Laurent > > On Oct 19, 2010, at 2:38 PM, David Epstein wrote: > >> Hi Jesse >> >> Thank you for your reply. >> >> I'm a doctoral student and this is related to my personal research and >> projects. I will not be able to afford a commercial solution. Are there >> opensource solutions, like sesame or allegrograph? Is there a parser >> hook of some kind to insert the data into the store? >> >> The Tetherless_Map extension looks like it is specifically for >> geographic maps. So, that may not work. >> >> -david >> >> >> >> >> ------------------------------------------------------------------------------ >> Download new Adobe(R) Flash(R) Builder(TM) 4 >> The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly >> Flex(R) Builder(TM)) enable the development of rich applications that run >> across multiple browsers and platforms. Download your free trials today! >> http://p.sf.net/sfu/adobe-dev2dev >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: David E. <dav...@um...> - 2010-10-19 19:55:36
|
Thank you Yaron. I'm guessing the triple-store idea was proposed because it appears to let you assemble/connect small pieces of related data spread out over many pages. So, I could write to it inline the minute I read something interesting. Your solution sounds more feasible for my level of understanding. I've actually developed considerable skill in getting components to work--but far less skill in using them wisely. As you suggest, perhaps #set_internal is not for me either. Maybe a way to do this would be to (manually?) create an anchor for every paragraph in an article and then (manually?) link to those anchors from what I refer to as "cases". The links could be typed to show "supports" or "denies". With such a setup, is there a fairly easy way to (automatically) show the incoming links to each paragraph in an article? -david |
From: Yaron K. <ya...@gm...> - 2010-10-19 21:26:55
|
Hi, Okay. Just to clarify, I don't think there's anything wrong with using #set_internal - it all depends on whether you want to store one "case" per page, or many. To be able to link to any paragraph, the "Purple MediaWiki" extension might come in handy: http://www.mediawiki.org/wiki/Extension:Purple_MediaWiki I don't think there's any easy way to have each paragraph show the references to it, though. -Yaron On Tue, Oct 19, 2010 at 3:55 PM, David Epstein <dav...@um...> wrote: > Thank you Yaron. > > > I'm guessing the triple-store idea was proposed because it appears to > let you assemble/connect small pieces of related data spread out over > many pages. So, I could write to it inline the minute I read something > interesting. > > Your solution sounds more feasible for my level of understanding. I've > actually developed considerable skill in getting components to work--but > far less skill in using them wisely. > > As you suggest, perhaps #set_internal is not for me either. Maybe a way > to do this would be to (manually?) create an anchor for every paragraph > in an article and then (manually?) link to those anchors from what I > refer to as "cases". The links could be typed to show "supports" or > "denies". With such a setup, is there a fairly easy way to > (automatically) show the incoming links to each paragraph in an article? > > > -david > > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: David E. <dav...@um...> - 2010-10-20 05:40:31
|
Hi folks, Yaron, thank you for the tip. Purple MediaWiki is really a nice extension for targeting links into journal articles or other long documents. There must be half-a-dozen ways to proceed from here. What I've done is create a page for themes/concepts/cases that will be discussed in multiple articles and used #set_internal to create a sort of "typed link" into the article(s) as shown below. I then use a similar #ask at the bottom of the article(s) to show the same information about pages pointing to it. This seems completely usable--right now. But, I'm worried that it will not scale well. I'll eventually need ways to summarize results both on the themes/concepts/cases pages and the article pages. Is there a way to do SQL style counts or aggregation with #ask? Or perhaps SemanticDrillDown on the properties created with #set_internal? NOTE: Data is from "Community Informatics for Community Development: Hope or Hype?" by Pitkin: ON CONCEPT PAGE "Community development" {{#set_internal:IsTypedLink |HasLabel={{PAGENAME}} |HasType=Def |HasText=Community development can be defined broadly as strategies to build local capacity and improve the quality of life in geographic communities | HasLink=http://localhost/newbrain/index.php/Community_Informatics_for_Community_Development:_Hope_or_Hype%3F#hid2A }} {{#set_internal:IsTypedLink |HasLabel={{PAGENAME}} |HasType=Def |HasText=Community development is asset building that improves the quality of life among residents of low- to moderate-income communities, where communities are defined as neighborhoods or multineighborhood areas. |HasCite=Ferguson and Dickens, 1999, p. 5 | HasLink=http://localhost/newbrain/index.php/Community_Informatics_for_Community_Development:_Hope_or_Hype%3F#hid4E }} {{#ask:[[IsTypedLink::+]][[HasLabel::{{PAGENAME}}]] |mainlabel=- |? HasType |? HasText |? HasCite |? HasLink }} AT BOTTOM OF ARTICLE PAGE: (Luckily the filter catches the article page name even though instances have Purple MediaWiki anchors. Anchors still work to jump into article.) {{#ask:[[IsTypedLink::+]][[HasLink::{{PAGENAME}}]] |mainlabel=- |? HasLabel |? HasType |? HasText |? HasCite |? HasLink }} |