Hi John,
thanks for the link.
On 27 August 2014 21:34, John McClure wrote:
> Without a specified value, then the object is unspecified
> ... so the model you wonder about becomes just "subject-predicate"
> ... thereby breaking the predominant model we live with
No, you confuse the empty (i.e.
Triple = "subject-predicate-object" all are required
Without a specified value, then the object is unspecified
... so the model you wonder about becomes just "subject-predicate"
... thereby breaking the predominant model we live with
I suppose http://www.w3.org/TR/rdf11-mt/ can explain in more
Thanks, James. That answers the first question: It has been a
conscious design decision, i.e. it's a feature.
On 27 August 2014 20:32, James HK wrote:
> Hi,
>
> [0] prevents text/string values of being empty.
>
> [0]
> https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/includes/
Hi,
[0] prevents text/string values of being empty.
[0]
https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/includes/datavalues/SMW_DV_String.php#L16
PS: Haven't look at the issue itself but [0] should explain the
current codified behaviour.
Cheers
On 8/28/14, Stephan Gambke w
On 2014-08-27 19:20, John McClure wrote:
> In the world of triples, you're asking about something less
> Neither a feature nor a bug -- it's an ontological reality
I do not understand that statement. Could you elaborate?
---
On 2014-08-27 18:04, Nathan Douglas wrote:
> IMHO being able to make a relationship between something and nothing
> isn't terribly useful. If you have a page about goats, you don't have
> to specify that its capital city is nil, etc.
I do not want to specify nil, I want to specify a string of len
In the world of triples, you're asking about something less
Neither a feature nor a bug -- it's an ontological reality
On 8/27/2014 6:15 AM, Stephan Gambke wrote:
> It is not possible to store empty strings/texts, like this:
> [[Foo::]]
> {{#set:Foo|}}
>
> Bug or feature? And if feature, what's th
