Re: Incrementing a literal

On 12 Nov 2012, at 14:24, Сергей Ларионов <s.larionov@rks.karelia.ru> wrote:

> 
> Melvin, may I propose an opinion that 'needing to
> update a value' seems like a design flaw. Why? Taking
> your particular example of incrementing a 'counter'
> variable which goes from 1 to 2 to 3 and further on,
> on each step there actually *was* a time/state when
> 'counter' contained each of it's values. And at that
> time/state conclusions could be made which were based
> on *that* particular value. Updating seems like
> effectively erasing the history.
> 
> Now what is 'current value' as it obviously should
> have some means to be changed? Well 'current value' 
> seems like a result of a function taking a specific
> 'current' time as an input. Current time is an observer's 
> context property. So may an answer to your question 
> contain a suggestion to store all the values for a 
> counter with their relevant time frame attributes 
> and obtain 'current' value using a query? SL

that is impossible since time is continuous and between any 
two times there are infinite number of more time slots. You
would need temporal reasoning and mereological reasoning to do
this. Those tools are not available yet.

> 
> 
>> Is there a pattern for incrementing a literal counter?
>> Alice stores turtle in http://example.org/counter
>> The initial operation should generate something like
>> <#> <#counter> 1.
>> Then the subsequent operation
>> <#> <#counter> 2.
>> And after that.
>> <#> <#counter> 3.
>> And so on ...
> 
>> Is there a neat way to do this in  distributed way?  SPARQL update?   Maybe using Etags?   
> 
> 
> 

Social Web Architect
http://bblfish.net/