In preparation of SMW 1.5, I am currently doing some large-scale changes to
certain internals of the SMW code. This involves changes in the way in which
multi-valued properties (a.k.a. n-ary properties) are handled. Eventually,
only very little will change from a user's perspective (only a
Hi,
The change will also introduce some fixed limit on how many values a multi-
valued property can at most have. It is currently set to 5. If you have any
such properties with more than 5 values then please let me know.
If I understand correctly you mean the number of value-parts a
On Mittwoch, 6. Januar 2010, zehet...@molgen.mpg.de wrote:
Hi,
The change will also introduce some fixed limit on how many values a
multi- valued property can at most have. It is currently set to 5. If you
have any such properties with more than 5 values then please let me know.
If I
Hi,
I'm not sure what the maximum is right now, between 10 and 20 but the point is
that tomorrow a dataset could come along which has 50 or more parts. So having
any fixed value, especially one which can only be changed by modifying the code
itself, is a serious drawback although I assume you
On Mittwoch, 6. Januar 2010, Patrick Nagel wrote:
Hi Markus,
On 2010-01-06 09:27 UTC Markus Krötzsch wrote:
The change will also introduce some fixed limit on how many values a
multi- valued property can at most have. It is currently set to 5.
If you have any such properties with more
On Mittwoch, 6. Januar 2010, zehet...@molgen.mpg.de wrote:
Hi,
I'm not sure what the maximum is right now, between 10 and 20 but the point
is that tomorrow a dataset could come along which has 50 or more parts. So
having any fixed value, especially one which can only be changed by
Hi all,
Forgive me if I misunderstand or am off topic
The idea of internal objects is very interesting and I appreciate the
description of SIO versus SMW native objects. What I am wondering is if the
idea of internal objects could be extended to complex objects like tables. One
could
