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
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 be the
Hi Markus,
On 2009-08-03 14:57, Markus Krötzsch wrote:
Strictly speaking, a type is something that only a property has, so it could
be confusing to use it for values (I assume what you mean is some value
given
to the property 'has' the wrong type).
Ok, scratch that :) I shouldn't write
On Sonntag, 2. August 2009, Markus Krötzsch wrote:
...
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 stopped being viewed as errors in
general.
The
On Montag, 3. August 2009, Patrick Nagel wrote:
Hi Markus,
On 2009-08-03 14:57, Markus Krötzsch wrote:
Strictly speaking, a type is something that only a property has, so it
could be confusing to use it for values (I assume what you mean is some
value given to the property 'has' the wrong
2009/8/2 Yaron Koren yaro...@gmail.com:
Keeping with my preference for having property names be prepositional
phrases, how about Has improper value for?
Has improper value for ++
Dan.
I should note that I hope that properties with blank values don't get
included in this accounting.
That's good news. And it's great news about blank values not getting counted
as errors! That should help out a lot of people who store data in templates.
-Yaron
On Mon, Aug 3, 2009 at 8:14 AM, Markus Krötzsch
mar...@semantic-mediawiki.org wrote:
By the way: however we call it, this property
