Re: Another question re: ACTION-920

yet another one (this is how far I got regarding ACTION-920 so far):

http://www.w3.org/2005/rules/wiki/DTB#func:sublist_.28adapted_from_fn:subsequence.29

4.11.4.4 func:sublist (adapted from fn:subsequence)

Note that this function as it stands so far is quite different from  
fn:subsequence. First, fn:subsequence has no ?stop position argument,  
but ?start ?length instead, second the domain for these two parameters  
as defined for fn:subsequence is xs:double)

I suggest to go with the way that fn:subsequence proposes, i.e.
?start ?length
instead of
?start stop

In general, I am afraid I need some more time to check all of the list  
functions, hope to be finished before the next telconf though.

best,
Axel



On 20 Sep 2009, at 10:33, Axel Polleres wrote:

> Sandro,
>
> was there a reason why you specified the domain of the position  
> argument in
>
>   http://www.w3.org/2005/rules/wiki/DTB#func:get
>
> to be xs:int?
>
> I changed that to xs:nonNegativeInteger, since it made more sense to  
> me.
>
> Please acknowledge.
>
> Axel
>
> On 20 Sep 2009, at 08:40, Axel Polleres wrote:
>
>> Started to clean up DTB wrt. List functions and predicates... cf.  
>> ACTION-920
>>
>> Question: Is
>>
>> External( pred: is-list( List ( 1 | 2 ) ) )
>>
>> true or false or undefined? From the current informal definition  
>> this is not clear.
>>
>> I adapted the definition of
>> http://www.w3.org/2005/rules/wiki/DTB#pred:is-list
>> assuming the former.
>> Further, I added the following examples to the definition of is- 
>> list in DTB:
>>
>>  is-list(List(0 1 2 | List(3 4))) = True
>>  is-list(List(1 | 2)) = True
>>
>> BTW, this is not RIF syntax, so the examples for lists in the  
>> document need to be
>> in proper RIF presentation syntax,  ie. instead it should be:
>>
>> External(pred:is-list(List(0 1 2 | List(3 4)))) will evaluate to t  
>> in any interpretation.
>> External(pred:is-list(List(1 | 2))) will evaluate to t in any  
>> interpretation.
>>
>>
>> I am not sure whether I manage to clean up all list functions, but  
>> I think we cannot have
>> examples in the document which aren't valid for any syntax we  
>> support, so at least the examples should be cleaned up.
>> Given ambiguities of the informal mappings like thes further  
>> convinces me that it we
>> probably don't want the informal mappings in the spec. Opinions?
>> (I am still not sure how far I get with the cleaning...)
>>
>>
>> Axel
>>
>>
>>
>> -- 
>> Dr. Axel Polleres
>> Digital Enterprise Research Institute, National University of  
>> Ireland, Galway
>> email: axel.polleres@deri.org  url: http://www.polleres.net/
>>
>>
>>
>
> -- 
> Dr. Axel Polleres
> Digital Enterprise Research Institute, National University of  
> Ireland, Galway
> email: axel.polleres@deri.org  url: http://www.polleres.net/
>
>
>

-- 
Dr. Axel Polleres
Digital Enterprise Research Institute, National University of Ireland,  
Galway
email: axel.polleres@deri.org  url: http://www.polleres.net/

Received on Sunday, 20 September 2009 10:30:41 UTC