On Sonntag, 2. August 2009, Patrick Nagel wrote:
> Hi Markus,
>
> first of all, thanks for the upcoming new release! Highly appreciated :)
>
> On 2009-08-02 21:32, Markus Krötzsch wrote:
> > The upcoming SMW release 1.4.3 will introduce a property that helps to
> > find input errors: its value will
On Sonntag, 2. August 2009, Jeff Thompson wrote:
> Suppose "my date property" is "birthdate". Instead of [[birthdate::not a
> date]], I think it be the other way around:
> [[not a date::birthdate]]
> so that it won't be confused with other property values for birthdate.
I think there is still some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Markus,
first of all, thanks for the upcoming new release! Highly appreciated :)
On 2009-08-02 21:32, Markus Krötzsch wrote:
> The upcoming SMW release 1.4.3 will introduce a property that helps to find
> input errors: its value will be the page
Suppose "my date property" is "birthdate". Instead of [[birthdate::not a
date]], I think it be the other way around:
[[not a date::birthdate]]
so that it won't be confused with other property values for birthdate.
Markus Krötzsch wrote:
> The upcoming SMW release 1.4.3 will introduce a property t
On Sonntag, 2. August 2009, Yaron Koren wrote:
> Keeping with my preference for having property names be prepositional
> phrases, how about "Has improper value for"?
Ok, preference noted.
>
> I should note that I hope that properties with blank values don't get
> included in this accounting. Spea
Keeping with my preference for having property names be prepositional
phrases, how about "Has improper value for"?
I should note that I hope that properties with blank values don't get
included in this accounting. Speaking of which, let me note that I also
think it would be great if blank values s
The upcoming SMW release 1.4.3 will introduce a property that helps to find
input errors: its value will be the page of the property that the wrong value
was assigned to. For example, if you put
[[my date property::not a date]]
on page "Test1" (where the property would expect a valid date), the
Temlakos,
this is quite a lot of affected code. I am still about to prepare the SMW
1.4.3 release, so I do not include the new messages in SVN yet (since there is
no code using them anyway).
For simplifying review and inclusion, it would be very useful if you could
split your contribution by f