I was speaking theoretically - I don't have a practical example but I can
imagine automatically building annotations from other sources, with values
that we may not necessarily want to show on a wiki page.
For example, aliases or mappings of a page name to internal IDs in several
databases. You would need this type of annotation to do further queries and
you would currently implement that with 'silent' annotations somewhere on
the page (or in a template).
It could be useful to move them in a related page in a separate namespace to
both avoid confusing casual editors of the page and prevent manual edits of
these annotations.
- Laurent
On Wed, Apr 6, 2011 at 9:16 AM, Yaron Koren <ya...@wikiworks.com> wrote:
> Hi,
>
> I'm confused about a few things - John:
>
> - what do you mean by "logical properties" and "presentation properties"?
> - what's a "spo statement"?
>
> And Laurent - what would be an example of a "complex, arcane annotation"?
>
> -Yaron
>
> On Tue, Apr 5, 2011 at 10:02 PM, John McClure <jmccl...@hypergrove.com>wrote:
>
>> Hmm you raise some interesting possibilities however it seems that a
>> generic capability to store spo triples about any wikipage is much more
>> ambitious than what I'm suggesting. In my proposal, queries do not change
>> whatsoever; howebver the SH approach would involve compound queries, first
>> of the subject-page's own triples, and then of the other-namespace-page's
>> set of triples to identify those whose subject is the subject-page. That
>> said, your suggestion is an absolute requirement for instance in the legal
>> arena whose documents have nothing BUT spo statements (albeit couched in
>> lovely legalese) that is of course, if one is not interested in documents
>> being the result of a massive number of cascading transclusions!!! Thanks
>> for your thoughts. John
>>
>> -----Original Message-----
>> *From:* lalqu...@gmail.com [mailto:lalqu...@gmail.com]*On Behalf Of *Laurent
>> Alquier
>> *Sent:* Tuesday, April 05, 2011 2:19 PM
>> *To:* jmccl...@hypergrove.com
>> *Cc:* Yaron Koren; semediawiki-devel@lists.sourceforge.net
>> *Subject:* Re: [SMW-devel] Talkspace Semantics
>>
>> I can see a use for this sort of thing with any automated annotation
>> application.
>>
>> It would be nice to have a way to store complex, arcane annotations
>> without overloading the wiki page itself.
>>
>> It doesn't have to be in the talk page, maybe a separate name space
>> altogether, but being able to extend annotations of one page to the same
>> page in a different name space could have some benefits.
>>
>> A practical example is the Semantic History extension :
>> http://www.mediawiki.org/wiki/Extension:SemanticHistory
>>
>> Having these annotations in a separate namespace and still related to the
>> original page would help.
>>
>> - Laurent
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Xperia(TM) PLAY
>> It's a major breakthrough. An authentic gaming
>> smartphone on the nation's most reliable network.
>> And it wants your games.
>> http://p.sf.net/sfu/verizon-sfdev
>> _______________________________________________
>> Semediawiki-devel mailing list
>> Semediawiki-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>>
>>
>
>
> --
> WikiWorks · MediaWiki Consulting · http://wikiworks.com
>
--
- Laurent Alquier
http://www.linfa.net
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
