've got problems with smw, but I think it's the configuration of
our server.
When I create a simple relation in the wiki, our CPU us grow and stay
at this level permanently...
top - 01:04:55 up 6:18, 1 user, load average: 3.02, 3.01, 2.46
Tasks: 108 total, 4 running, 104 sleeping, 0 stopped, 0 zombie
Cpu(s): 77.7% us, 1.3% sy, 0.0% ni, 19.1% id, 1.8% wa, 0.0% hi,
0.0% si
Mem: 3106312k total, 1339136k used, 1767176k free, 88184k buffers
Swap: 4088500k total, 0k used, 4088500k free, 485116k cached
then I restart apache and mysql:
top - 01:06:56 up 6:20, 1 user, load average: 2.19, 2.86, 2.48
Tasks: 84 total, 1 running, 83 sleeping, 0 stopped, 0 zombie
Cpu(s): 12.0% us, 0.6% sy, 0.0% ni, 85.0% id, 2.4% wa, 0.0% hi,
0.0% si
Mem: 3106312k total, 804360k used, 2301952k free, 88192k buffers
Swap: 4088500k total, 0k used, 4088500k free, 485628k cached
It's sytematic...
Did someone have an idea to help us? we use the last, and upgraded
smw version, but I'm sure smw in not the problem.
Kind regards,
Hughes-Jehan
Tony Bowden wrote:
>
That's how I would approach it. My feeling is that this will be *far*
simpler than the current inline queries, and looking at them too hard
will only make the resulting code more complex rather than as simple as
possible. So, a bit copy and paste to get it started, and later refactor
to have less code repetition.
Or else there is someone who was enough insight to provide an
architecture for this up front, but I doubt it :)
cheers,
denny
On 10/8/06, Christopher Baker <slithytove2@...> wrote:
>
> On 10/8/06, S Page <skierpage@...> wrote:
> >
> > Enhancing inline queries this way is worthwhile, but I imagine it will
> > be hella hard to code! Start at lines 477 and 523 in
> > SMW_InlineQueries.php.
> >
>
> why not just edit the code so that each page that is saved in a namespace
> with semantics create these attributes/relations?
>
1. Export
=========
Thomas Bleher wrote:
> I think it would be cool if SMW exported wiki page properties as
> attributes and relations.
>
Plain MediaWiki's Special:Export exports the contributor and timestamp
of the latest revision in XML.
If you were to enhance this, why not export them as Dublin Core metadata
in RDF? That's already a meaningful syntax for these properties.
Another project has done this, "Wikipedia3", see e.g.
It was announced on the swikig mailing list
( )
and Markus Krötzsch responded
( ):
However, we thought about creating a
meta-data complement of our RDF-export as well (where you have author,
license, revision, etc. all in one place).
As Markus pointed out, SMW's Special:Export RDF currently exports the
facts in the article, not facts about the article. The two are
separate; for example, [[last edited by::John Hancock] in the
Declaration of Independence article is usually talking about the
historic document, not about the Wiki page for it.
> I'm thinking of the following:
> Attributes:
> Last edit at
> Created at
> Edit count
> Page size
> Relations:
> Created by
> Edited by
> Last edit by
> (I'm no native speaker, so maybe the names should be changed; I think
> the idea is clear)
>
2. Querying
===========
> This would allow a lot of useful things:
> * The front page could list newly created pages
> * Category pages could list newly created pages, the pages last edited
> or the biggest and smallest pages
> * Users could get a list of pages they had edited or created, e.g.
> <ask>[[Created by::Thomas]] [[Last edit by::*]] [[Last edit at:=*]]</ask>
>
Ahh, you're not really asking for export of page properties *from*
Semantic MediaWiki, you're asking for access to page properties *within*
SMW. That's different, but still an interesting idea.
Some page properties are already available as variables in Wiki text
like {{REVISIONID}}, see. And the
raw information is in the MediaWiki tables, primarily in the page and
revision tables.
However, to do your useful things you want to query this information
using the SMW inline query syntax, and the MediaWiki variables don't
help. Yes you might be able to do this as you propose: export page
metadata information, then reimport it as special SMW relations and
attributes. It would be more direct if you abstracted the powerful
inline query facility in SMW so that queries on certain special terms
turn into database queries against other tables than the smw_attribute
and smw_relation tables:
* Querying for your "Last edit by" would query against the revision table.
* Querying for "Has type", "Main display unit", "Imported from", etc.
would query against the smw_specialprops table.
* If the Wikidata project takes off, querying against other special
properties would query the appropriate dedicated Wikidata table.
Enhancing inline queries this way is worthwhile, but I imagine it will
be hella hard to code! Start at lines 477 and 523 in SMW_InlineQueries.php.
Best,
--
=S Page
> In short, with these attributes and relations, SMW can emulate many
> special pages, and make them more powerful and useful.
>
> Unfortunately, I don't currently have time to implement this, so I
> thought I'd post it here; maybe someone wants to code this up :-)
>
> What do you think about this idea?
>