W3C home > Mailing lists > Public > public-rdf-text@w3.org > April to June 2009

Re: new version of rdf:O)-> document

From: Alan Ruttenberg <alanruttenberg@gmail.com>
Date: Mon, 1 Jun 2009 02:03:59 -0400
Message-ID: <29af5e2d0905312303m67d5047fi15c108154f834cd8@mail.gmail.com>
To: sandro@w3.org, phayes@ihmc.us, der@hplb.hpl.hp.com, public-rdf-text@w3.org, "Peter F.Patel-Schneider" <pfps@research.bell-labs.com>
Some editorial comments:

Table 1:

...all strings of the form "abc" and all pairs of the form ( "abc" ,
"lc-langtag" )
such that "abc" is contained in the subset of xs:string determined by ( F v
)
as specified by XML Schema Datatypes [XML Schema Datatypes].

->

...all strings of the form "abc" and all pairs of the form ( "abc" ,
"lc-langtag" )
such that "abc" is contained in the subset of the value space of
xs:string determined
by ( F v )
as specified by XML Schema Datatypes [XML Schema Datatypes].
--

In descriptions of the value space of plan literals in
http://www.w3.org/TR/rdf-mt/ language tagged values are written using "<" an
">" to group the tuple. In this document we use "(" and ")". I'd suggest
using the "<" and ">" delimiters for consistency.

-- 

5.1 Functions for Assembling and Disassembling rdf:PlainLiteral Data Values

This function: rtfn:text-from-string( $arg1 as xs:string ) as
rdf:PlainLiteral, seems unecessary - it is the identity operation if this is
a function on values.

--

rtfn:text-from-string: "Note that, since the lexical forms of
rdf:PlainLiteral" - it doesn't matter what the lexical forms are, it matters
what the values are.

--

"returns the string part s from the argument $arg, which must be an
rdf:PlainLiteral data value of the form ( s, l ) or of the form s"

->

"returns the string part s if $arg  is a rdf:PlainLiteral data value of the
form ( s, l ) or of the form s"

This parallels the definition for rtfn:lang-from-text and removes the
confusing "must be a" which might suggest that there are PlainLiterals with
some other form than those given.

--

empty sequence as argument to functions:

>From http://www.w3.org/TR/xpath-functions/#func-signatures:  Some functions
accept a single value or the empty sequence as an argument and some may
return a single value or the empty sequence. This is indicated in the
function signature by following the parameter or return type name with a
question mark: "?", indicating that either a single value or the empty
sequence must appear.

In rtfn:compare the comparands can be the empty sequence. However in the
functional style definitions of the functions the comparands are passed
to rtfn:lang-from-text and rtfn:string-from-text which can not take the
empty sequence.

-- 

There are still an editor's note: These functions have not yet been renamed.
The word "text" in the function names may change to "plain-literal", and the
namespace may change from .../rdf-text-functions to
.../plain-literal-functions

What is the disposition here? Note that this would also effect the
definition of "rtfn" above. Would "rtfn" change to "plfn"?

--

We had discussed including a note explaining that while RDF cited RFC 3066
we interpreted that as really citing the latest version of the language tag
spec, and since BCP 47 supersedes 3066, the possible values of language tags
for both plain literal and rdf:PlainLiteral are the same.

--

Acknowledgments: I suggest adding wording noting the contribution of the
SPARQL LC comment and members of the SPARQL WG.

Editors: I suggest adding Peter and Sandro.

Contributors: I suggest adding Pat Hayes.

-Alan
Received on Monday, 1 June 2009 06:04:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 1 June 2009 06:04:53 GMT