- From: Axel Polleres <axel.polleres@deri.org>
- Date: Fri, 03 Apr 2009 18:28:45 +0100
- To: Axel Polleres <axel.polleres@deri.org>
- CC: "Phillips, Addison" <addison@amazon.com>, Jos de Bruijn <debruijn@inf.unibz.it>, Alan Ruttenberg <alanruttenberg@gmail.com>, Jie Bao <baojie@gmail.com>, Sandro Hawke <sandro@w3.org>, "public-rdf-text@w3.org" <public-rdf-text@w3.org>, "team-rif-chairs@w3.org" <team-rif-chairs@w3.org>, "team-owl-chairs@w3.org" <team-owl-chairs@w3.org>
I just did a run over the document. Please let me know whether the
changes are acceptable:
* in Section 5.1.1 fn:text-from-string, I merged the old
fn:text-from-string with fn:text-from-string-lang, jsut making the lang
argument optional.
Also, I addressed Boris' original EdNote on converion of lang tags to
lower case. However, I left another EdNote, since there are indeed 2
options (converting to lowercase or not), I personally prefer
converting, so I left:
{{EdNote|[[User:AxelPolleres|Axel Polleres]] 03 april 2009| RDF requires
language tags to be in lowercase. To minimize the discrepancy with RDF,
the lexical forms of rdf:text also require language tags to be in
lowercase. This function should be more explicit about how it handles
the case. There two possibilities: either it requires the language tag
argument to be in lowercase (and raises an error if it is not), or it
simply converts $arg2 to lowercase. At the moment, the latter option was
chosen.}}
Please let me know whether this is fine, so I can remove the Ed note.
I won't fight if a majority claims lowercase strings allowed only, either.
* in Section 5.1.2 fn:string-from-text I addressed and removed
{{EdNote|[[User:Bmotik2|Boris Motik]] 27 march 2009| This function
should be modified such that it accepts in $arg both values with a
language tag as well as values without it.}}
* in Section 5.1.3, I addressed and removed
{{EdNote|[[User:Bmotik2|Boris Motik]] 27 march 2009| This function
should be modified such that it accepts in $arg both values with a
language tag as well as values without it. In the latter case, the
function could return the empty string.}}
* in Section 5.2.1
{{EdNote|[[User:Bmotik2|Boris Motik]] 27 march 2009| This function
should be modified such that it accepts both values with a language tag
as well as values without it.<br /><br /> There is, however, an
alternative way of handling this. Since xs:string values are now
rdf:text data values, would it be possible to simply extend the
fn:compare function from XQuery? That is, the definition of fn:compare
would be extended such that it accepts all four combinations of
arguments. This would be quite beneficial to the users, as they would
not need to fiddle with different functions.}}
Hmmmm, I agree with the latter, but it will need to get back to the
XQuery/XPath group.
* As for text-length,
{{EdNote|[[User:AxelPolleres|AxelPolleres]] 12 November 2008
(UTC)|'''Open Issues''': The inclusion of text-length, as well as the
definition of the function - whether the length of an rdf:text value
should concern only the string part - are still under discussion.}}
I thought about it again... the easiest solution seems to be to indeed
drop it. We can emulate the respective facets in RIF still by extraction
and respective string functions.
* in Section 5.3.2 I addressed and removed
{{EdNote|[[User:Bmotik2|Boris Motik]] 27 march 2009| This function
should be modified such that it accepts both values with a language tag
as well as values without it. Furthermore, it should be made precise
whether the language range is the basic or the extended one.}}
please check,
Axel
--
Dr. Axel Polleres
Digital Enterprise Research Institute, National University of Ireland,
Galway
email: axel.polleres@deri.org url: http://www.polleres.net/
Received on Friday, 3 April 2009 17:29:28 UTC