On Freitag, 25. Juli 2008, Steren wrote:
> Hello,
> I played a bit with my local installation of SMW 1.2 and SMWsvn and noticed
> a bug : Inline queries don't refresh after the deletion of a property.
>
> Here is the basic scenario : (This behavior can be reproduced on the
> sandbox http://sandbox.
Hello,
I played a bit with my local installation of SMW 1.2 and SMWsvn and noticed
a bug : Inline queries don't refresh after the deletion of a property.
Here is the basic scenario : (This behavior can be reproduced on the sandbox
http://sandbox.semantic-mediawiki.org/wiki/Testpage )
- Add propert
2008/7/24 Sergey Chernyshev <[EMAIL PROTECTED]>:
> Nathan, Asheesh,
>
> How's it going with RDFa support project? I'm happy to be in conversations
> and help the developer with advise or even code - please let the list know.
>
> Thank you,
>
> Sergey
Sergey,
Thanks for the reminder. I
Hi,
Sorry, I didn't mean that you were doing too much work, just that it's too
much work to require every administrator to do.
And a "Forbid nulls" special property would be a nice idea.
-Yaron
On Thu, Jul 24, 2008 at 1:16 PM, Temlakos <[EMAIL PROTECTED]> wrote:
> Yaron:
>
> Maybe it's a lot o
Yaron:
Maybe it's a lot of work, but I have another reason to use #if
statements: formatting. My templates are either "infoboxes" or else are
query-driven and thus in no danger of producing a null annotation. And a
dangling infobox line looks worse than a null-value warning.
Temlakos
Yaron Ko
Nathan, Asheesh,
How's it going with RDFa support project? I'm happy to be in conversations
and help the developer with advise or even code - please let the list know.
Thank you,
Sergey
On Sat, Jun 21, 2008 at 1:53 PM, Sergey Chernyshev <
[EMAIL PROTECTED]> wrote:
> Yep, thanks for
Allow null values by default; but perhaps also allow a way to make
null values verboten for a given property or type. E.g., an "Forbid
nulls" special property.
--
Jonathan "Dataweaver" Lang
-
This SF.Net email is sponsored
Hi,
Yes, it's possible to get around this problem using #if statements, but that
seems like an awful lot of work: an #if call for every field in every
template.
And null values wouldn't have to be stored in the semantic-property tables,
just like (I assume) they're not stored now, so there wouldn
Yaron:
Are you sure that's necessary? Whenever I write a semantic template, I
use {{#if: statements to make sure that no annotation takes place unless
the relevant parameter exists. And a null number strikes me as a
show-stopper if we ever wanted to do arithmetic with those annotated
numbers.
Hi,
Currently semantic properties all display a warning message when they're
given a null value (e.g., [[Has country::]]). That makes sense if all
properties are hand-coded, but if a site uses semantic templates, it could
easily end up with many blank values. [1] Each of those gets a little
warni
I've got just one or two more small notes that might help people out
(might want to add them to the readme as well):
A very useful little trick on linux (heck, this would probably work in
cygwin as well) for using the environment variable is to cd into the
root of your MediaWiki install and run
11 matches
Mail list logo
