Thanks for this, and pointing me to the Purple MediaWiki extension.
MashaJS looks like a very interesting piece of the puzzle, too, I
look forward to playing with it.
I'll keep the list updated with my strategies for dealing with this
stuff. Hopefully a useful extension or two will come out of it.
Also, on MashaJS, I think it would be nice if its references used
RFC 5147 to refer to the selected text. It's a simple, readable url
scheme (of the form: &char=5,20), and using a RFC backed standard is
a nice thing to do for something like HTML fragments, where we
potentially want to refer to them semantically. Oh, and RFC 5147 is
also likely to be adopted as an option for Xinclude 1.1. But I
haven't looked at MashaJS closely yet, maybe there are good reasons
for choosing their scheme.
Thanks again for your thoughts, Yury!
On Fri, Sep 21, 2012 at 06:52:08PM +0400, Yury Katkov wrote:
> Please inform about your progress in this direction! Here is yet another
> approach to fine-grained access: http://mashajs.com/index_eng.html , http://
> http://www.mediawiki.org/wiki/Extension:MashaJS. When we though about those things we
> face again and again the nature of the wiki and the impossibility to find the
> universal solution: the paragraph I'm pointing to can change, merged with
> another paragraph or be erased every moment.
> As a workaround we now use Semantic forms with many Textarea fields. Each field
> holds some amount of text.
> Yury Katkov
> On Fri, Sep 21, 2012 at 6:42 PM, Nick White <nick.white@...> wrote:
> On Fri, Sep 21, 2012 at 06:09:09PM +0400, Yury Katkov wrote:
> > The main problem is that the wikipage is an ever-changing object. Here is
> > another approach to fine-grained access: http://www.mediawiki.org/wiki/
> > Extension:Purple_MediaWiki
> Aha, that is interesting. Thanks for pointing it out; I hadn't seen
> it before.
> What I would *ideally* like would be a way to use make semantic
> statements about the anchor links, and then be able to hook in to
> the semantic media wiki stuff to browse and search them.
> An example of how I would dream this stuff to work:
> - I have 4 pages, each short essays, all about Lewis Carroll (and
> marked appropriately with semantic mediawiki)
> - 2 of these essays deal with his death, one starting on the 5th
> paragraph, the other on the 12th.
> - Each of those paragraphs are marked up semantically with
> - I can then browse Lewis Carroll -> Themes; see that two of the
> essays reference it, and then (crucially) click on one *and be
> taken to the appropriate section of the essay.*
> The location of something in a text sounds like a boring detail, but
> in my case it's not. Ideally I'd like to encode it semantically, so
> that the data can be interrogated by a variety of different tools,
> and be easily shared outside of my wiki project.
> Is there a way to refer to page anchors in Semantic Mediawiki's
> property setting? Would there be an obvious way to for me to add it
> with an extension (I'm happy to write my own)?
> To make the above use-case work, does it sound like my best bet is
> writing an extension or two to allow referring to HTML anchors in
> SMW statements? Or might there be a better way of thinking about it?
> > On Fri, Sep 21, 2012 at 3:52 PM, Nick White <nick.white@...>
> > I'm newish to the Semantic Mediawiki world, so apologies for any
> > ignorance (I am planning to go to SMWCon next month though, which
> > should dispell a lot of that.)
> > In general semantic mediawiki refers to things which are represented
> > as pages. So you'll have a page called "Berlin", which has
> > [[Population::100000]], or whatever. RDF can obviously refer to
> > anything you care to name, with xpointer or whatever.
> > What I want to do is have a page of text, and assign properties to
> > certain parts of it. So for example assign lines 10 - 12 the
> > property [[Theme::death]]. RDF is up to the challenge, and the
> > OpenAnnotation vocabulary (http://openannotation.org) looks like it
> > will be useful for that. But I'm wondering if Semantic Mediawiki has
> > any support (or extensions) for doing this kind of marking up? Or
> > using said markup? Is there a good way to refer to something other
> > than the page, within smw?
> > If not, can one embed extra metadata like this into a page, which I
> > could then interrogate as appropriate with an extension I write?
> > Thanks for any advice,
> > Nick White
> > Got visibility?
> > Most devs has no idea what their production app looks like.
> > Find out how fast your code is with AppDynamics Lite.
> > http://ad.doubleclick.net/clk;262219671;13503038;y?
> > http://info.appdynamics.com/FreeJavaPerformanceDownload.html
> > _______________________________________________
> > Semediawiki-user mailing list
> > Semediawiki-user@...
> > https://lists.sourceforge.net/lists/listinfo/semediawiki-user