Hi Markus,
http://semantic-mediawiki.org/wiki/Semantic_MediaWiki_1.5.0
doesn't mention any restriction in the number of 'fields' of an n-ary property
as it was mentioned in earlier announcements.
Has this new limitation been implemented in 1.5 and if so, what is the limit and
any advice how to
On Donnerstag, 4. März 2010, zehet...@molgen.mpg.de wrote:
Hi Markus,
http://semantic-mediawiki.org/wiki/Semantic_MediaWiki_1.5.0
doesn't mention any restriction in the number of 'fields' of an n-ary
property as it was mentioned in earlier announcements.
Has this new limitation been
Hi,
well the number of possible fields in n-ary properties is a make or break
criteria for me to be able to use MW/SMW, so it's a point I don't dare to lose
out of sight.
Right now the largest properties I added to the wiki have 15 to 20 fields (but
there are potential data with 60+).
On Donnerstag, 4. März 2010, Bob MacCallum wrote:
Looking at the upgrade instructions, it's not clear if I should edit
the Property pages to add [[Has type:Record]] etc before or after the
upgrade. Please advise. Thanks!
Good point. The best way is to first upgrade and then change the pages
On Donnerstag, 4. März 2010, CNIT wrote:
03.03.2010 20:21, Markus Krötzsch пишет:
Oh, and I also forgot about this question ...
On Donnerstag, 7. Januar 2010, Solbrig, Harold R. wrote:
Markus,
I am trying to visualize how this information would be represented in
RDF. If we are
Dear all,
I just have added a new extension to MediaWiki's SVN that we have been talking
about for a while now: SMWWriter, an API for editing facts in SMW easily.
You will find a rather extensive Documentation here:
http://semantic-mediawiki.org/wiki/Help:SMWWriter
Since this is my first API
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
besides the xofmonth hack, I created another extension a while ago that
modifies how multi-day
events are handled.
Usually (and without any better knowledge) if you have an event that starts on
April 8th and ends on
April 10th, you only
Well, I think the basic 'xofmonth' functionality is the way to go - a single
new value that takes care of everything. Assuming the new code works, I can
add it in to SMW myself, since #set_recurring_event is basically my code.
I'll probably wait until after SMW 1.5 is released, though...
For the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For the name of the new value, though, how about 'dayofweekinmonth'
instead? It's quite long, but it's the only thing I can think of where
there's even a remote chance that someone would understand it just by
seeing the name.
You're right.. this
Does anyone else have a suggestion? :)
Normalization would show the day of a week is an attribute of a date. So:
* An #ask should be able to say ?Date.Weekday
* IOW, a Date is a first class object as much as, say, a Place is
* IOW, I'd like to see SMW standardize category:Dates and its properties
I submitted an enhancement based on a patch I made locally to extend Last
Modification Date to the RDF export functions and by extension, to the
triple store connector if there is one.
I didn't get around to produce a diff file yet, so I included the updated
files for now.
It would be nice to
11 matches
Mail list logo
