PlainLiteral

Editors

Jie Bao, Rensselaer Polytechnic Institute

Sandro Hawke, W3C/MIT

Boris Motik, Oxford University

Peter F. Patel-Schneider, Bell Labs Research, Alcatel-Lucent

Axel Polleres, DERI Galway at the National University of Ireland

1 Introduction

The Resource Description Framework [RDF] is defined to have an extensible system of typed literals, based on XML Schema datatypes [XSD], and also to have plain literals. In the RDF specification, plain literals differ from typed literals in that plain literals have no datatype and can optionally have a language tag, indicating the natural language of the content. (See Tags for Identifying Languages [BCP 47]). These options for expressing RDF literals complicate specifications which interact with RDF, such as RIF and OWL. Furthermore, RDF does not provide a name for the set of all plain literals, which, for example, prevents one from stating in RDFS or OWL that the range of some property must be a plain literal.

In response, this specification introduces a datatype called rdf:PlainLiteral. The datatype is in the "rdf:" namespace because it refers to parts of the conceptual model of RDF. This extension, however, does not change that conceptual model, and thus does not affect specifications that depend on it such as SPARQL [SPARQL]. The value space of rdf:PlainLiteral consists of all data values assigned to RDF plain literals, which allows RDF applications to explicitly refer to this set (e.g., in rdfs:range assertions).

Because RDF plain literals are already a part of RDF and SPARQL syntaxes, rdf:PlainLiteral literals are written as RDF plain literals in RDF and SPARQL syntaxes.

As with plain literals, this datatype can associate language tags with unicode strings, but it does not provide its own facilities for representing natural language utterances. Unicode bidirectional control characters [BIDI] may be used within these literals, like all other unicode characters. (Richer, XML-based representations such as XHTML [XHTML] and Ruby annotations [RUBY] can be expressed using the rdf:XMLLiteral datatype.)

2 Preliminaries

A character is an atomic unit of text. Each character has a Universal Character Set (UCS) code point [ISO/IEC 10646] (or, equivalently, a Unicode code point [UNICODE]) that MUST match the Char production from XML [XML] thus ensuring compatibility with XML Schema Datatypes, version 1.1 [XML Schema Datatypes]. Code points are sometimes represented in this document as U+ followed by a four-digit hexadecimal value of the code point.

A string is a finite sequence of zero or more characters. The length of a string is the number of characters in it. Strings are written in this specification by enclosing them in double quotes. Two strings are identical if and only if they contain exactly the same characters in exactly the same sequence.

A language tag is a string matching the langtag production from BCP 47 [BCP 47]. Furthermore, note that this definition corresponds to the well-formed rather than the valid class of conformance in BCP 47. A language tag MAY contain subtags that are not registered in the IANA Language Subtag Registry, although an rdf:PlainLiteral implementation MAY also choose to reject such invalid language tags.

This specification uses Uniform Resource Identifiers (URIs) for naming datatypes and their components, which are defined in RFC 3986 [RFC 3986]. For readability, URIs prefixes are often abbreviated by a short prefix name according to the convention of RDF [RDF]. The following prefix names are used throughout this document:

• the prefix name xs: stands for http://www.w3.org/2001/XMLSchema#
• the prefix name rdf: stands for http://www.w3.org/1999/02/22-rdf-syntax-ns#

The names of the built-in functions defined in Section 5 are QNames, as defined in the XML namespaces specification [XML Namespaces]. The following namespace abbreviations are used in Section 5:

• fn stands for the http://www.w3.org/2005/xpath-functions namespace
• plfn stands for the http://www.w3.org/2009/rdf-PlainLiteral-functions namespace

Whether an expression of the form pr:ln denotes an abbreviated URI or a QName should be clear from the context: only the names of the built-in functions in Section 5 are QNames; all other such expressions denote abbreviated URIs.

Datatypes are defined in this document along the lines of XML Schema Datatypes [XML Schema Datatypes]. Each datatype is identified by a URI and is described by the following components:

• The value space is a set determining the set of values of the datatype. Elements of the value space are called data values.
• The lexical space is a set of strings that can be used to refer to data values. Each member of the lexical space is called a lexical form, and it is mapped to a particular data value.
• The facet space is a set of facet pairs of the form ( F v ), where F is a URI called a constraining facet, and v is an arbitrary data value called a constraining value. Each such facet pair is mapped to a subset of the value space of the datatype.

A plain literal is a string with an optional language tag [RDF]. A plain literal without a language tag is interpreted in an RDF interpretation by itself. A plain literal with a language tag can be written as "abc"@langTag, and is interpreted in an RDF interpretation as a pair < "abc" , "langTag" >.

A typed literal consists of a string and a datatype URI [RDF] and can be written as "abc"^^datatypeURI. Given an RDF datatype identified by datatypeURI, an RDF datatyped-interpretation that includes the datatype interprets the typed literal as the data value that the datatype assigns to the lexical form "abc".

The italicized keywords MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY specify certain aspects of the normative behavior of tools implementing this specification, and are interpreted as specified in RFC 2119 [RFC 2119].

3 Definition of the rdf:PlainLiteral Datatype

The datatype identified by the URI http://www.w3.org/1999/02/22-rdf-syntax-ns#PlainLiteral (abbreviated rdf:PlainLiteral) is defined as follows.

Value Space. The value space of rdf:PlainLiteral consists of

• all strings, and
• all pairs of the form < "abc" , "lc-langtag" > where "abc" is a string and "lc-langtag" is a lowercase language tag.

Lexical Space. An rdf:PlainLiteral lexical form is a string of the form "abc@langTag" where "abc" is an arbitrary (possibly empty) string, and "langTag" is either the empty string or a (not necessarily lowercase) language tag. Each such lexical form is mapped to a data value dv as follows:

• If "langTag" is empty, then dv is equal to the string "abc" and
• If "langTag" is not empty, then dv is equal to the pair < "abc", "lc-langtag" > where "lc-langtag" is "langTag" normalized to lowercase.

Facet Space. The facet space of rdf:PlainLiteral is defined as shown in Table 1.

4 Syntax for rdf:PlainLiteral Literals

It follows from the above that in datatyped interpretations that include the rdf:PlainLiteral datatype, the value space of rdf:PlainLiteral contains exactly all data values assigned to plain literals (with or without a language tag). The rdf:PlainLiteral datatype thus provides an explicit way of referring to this set.

To eliminate another source of syntactic redundancy and to retain a large degree of interoperability with applications that do not understand the rdf:PlainLiteral datatype, the form of rdf:PlainLiteral literals in syntaxes for RDF graphs and for SPARQL is the already existing syntax for the corresponding plain literal, not the syntax for a typed literal. Therefore, typed literals with rdf:PlainLiteral as the datatype are considered by this specification to be not valid in syntaxes for RDF graphs or SPARQL.

To implement this design and provide this interoperability, applications that employ this datatype MUST use plain literals (instead of rdf:PlainLiteral typed literals) whenever a syntax for plain literals is provided, such as in existing syntaxes for RDF graphs and SPARQL results.

Additionally, systems may need similar restrictions for non-syntactic public interfaces. For instance, in extended SPARQL basic graph matching, the results of matching SPARQL basic graph patterns in an entailment regime that understands rdf:PlainLiteral MUST provide variable bindings in existing RDF plain literal form.

5 Functions on rdf:PlainLiteral Data Values

This section defines functions that construct and operate on rdf:PlainLiteral data values. The terminology used and the way in which these functions are described are in accordance with the XQuery 1.0 and XPath 2.0 Functions and Operators [XPathFunc]. Each function is identified by a QName [XML Namespaces]. The error codes used in this section are given in Appendix G of the XPath 2.0 specification [XPath20] and Appendix C of XQuery and XPath function specification [XPathFunc].

5.1 Functions for Assembling and Disassembling rdf:PlainLiteral Data Values

5.1.1 plfn:PlainLiteral-from-string-lang

plfn:PlainLiteral-from-string-lang( $arg1 as xs:string, $arg2 as xs:string) as rdf:PlainLiteral

Summary: returns the data value < $arg1, lowercase($arg2) > if $arg2 is present, and returns the data value $arg1 otherwise. Both arguments must be of type xs:string or one of its subtypes, and $arg2 — if present — must be a (nonempty) language tag; otherwise, this function raises type error err:FORG0006. Note that, since in the value space of rdf:PlainLiteral language are in lowercase, this function converts $arg2 to lowercase.

5.1.2 plfn:string-from-PlainLiteral

 plfn:string-from-PlainLiteral( $arg as rdf:PlainLiteral) as xs:string

Summary: returns the string part s if $arg is a rdf:PlainLiteral data value of the form < s, l > or of the form s. If $arg is not of type rdf:PlainLiteral, this function raises type error err:FORG0006.

5.1.3 plfn:lang-from-PlainLiteral

 plfn:lang-from-PlainLiteral( $arg as rdf:PlainLiteral ) as xs:lang

Summary: returns the language tag l if $arg is an rdf:PlainLiteral data value of the form < s, l >, and returns the empty string if $arg is an rdf:PlainLiteral data value of the form s. If $arg is not of type rdf:PlainLiteral, this function raises type error err:FORG0006.

5.2 The Comparison of rdf:PlainLiteral Data Values

The notion of collations used in this section is taken from Section 7.3.1 of XPath and XQuery function specification [XPathFunc].

5.2.1 plfn:compare

 plfn:compare( $comparand1  as rdf:PlainLiteral?, $comparand2 as rdf:PlainLiteral? ) as xs:integer?

 plfn:compare( $comparand1  as rdf:PlainLiteral?, $comparand2 as rdf:PlainLiteral?, $collation as xs:string )  as xs:integer?

Summary: if either $comparand1 or $comparand2 is not of type rdf:PlainLiteral, of if $collation is specified but is not of type xs:string, this function raises type error err:FORG0006. Otherwise, the function returns the empty sequence if one of the arguments is empty, if one of $comparand1 and $comparand2 has a language tag and the other one does not, or if the language parts of $comparand1 and $comparand2 are unequal; otherwise, this function returns -1, 0, or 1 depending on whether the value of the string-part of $comparand1 (or $comparand1 itself, respectively, if it has no language tag) is respectively less than, equal to, or greater than the value of the string-part of $comparand2 (or $comparand2 itself, respectively, if it has no language tag). The collation used by the invocation of this function is determined according to the rules in Section 7.3.1 of the XPath and XQuery functions specification [XPathFunc].

The first version of this function backs up the XQuery operators "eq", "ne", "gt", "lt", "le", and "ge" on rdf:PlainLiteral values.

The two functions may be viewed as declared XQuery functions with the following definitions:

declare function  plfn:compare( $comparand1 as rdf:PlainLiteral?, $comparand2 as rdf:PlainLiteral? ) as xs:integer?
 {
  return
    if ( fn:empty($comparand1) ) then $comparand1
    else if ( fn:empty($comparand2) ) then $comparand2
    else if ( fn:compare (  plfn:lang-from-PlainLiteral( $comparand1 ), plfn:lang-from-PlainLiteral( $comparand2 ) ) = 0 ) then
       fn:compare (  plfn:string-from-PlainLiteral( $comparand1 ), plfn:string-from-PlainLiteral( $comparand2 ) )
 }

declare function  plfn:compare( $comparand1  as rdf:PlainLiteral?, $comparand2 as rdf:PlainLiteral? $collation as xs:string ) as xs:integer?
 {
  return
   if ( fn:empty($comparand1) ) then $comparand1
   else if ( fn:empty($comparand2) ) then $comparand2
   else if ( fn:compare ( plfn:lang-from-PlainLiteral( $comparand1 ),   plfn:lang-from-PlainLiteral( $comparand2 ) ) = 0 ) then
       fn:compare (  plfn:string-from-PlainLiteral( $comparand1 ) ,  plfn:string-from-PlainLiteral( $comparand2 ), $collation)
 }

5.3 Other Functions on rdf:PlainLiteral Data Values

5.3.1 plfn:length

 plfn:length($arg as rdf:PlainLiteral) as xs:integer

Summary: returns the number of characters in the string part s if $arg is an rdf:PlainLiteral data value of the form < s, l > or a string value s, respectively. If $arg is not of type rdf:PlainLiteral, this function raises type error err:FORG0006.

This function may be viewed as a declared XQuery function with the following definition:

declare function  plfn:length($arg as rdf:PlainLiteral?) as xs:integer
 {
  return
     fn:string-length (  plfn:string-from-PlainLiteral( $arg ) )
 }

5.3.2 plfn:matches-language-range

 plfn:matches-language-range($arg as rdf:PlainLiteral?, $range as xs:string) as xs:boolean

Summary: This function is only defined if $arg is a sequence of length 0 or 1 of literals of type rdf:PlainLiteral and $range is of type xs:string; if the parameters do not satisfy these typing conditions, the function raises a type error err:FORG0006. If the typing conditions are fulfilled, the function returns true in case $arg is an rdf:PlainLiteral data value of the form < s, l > with l a language tag that matches the extended language range $range as specified by the extended filtering algorithm for "Matching of Language Tags" [BCP-47]; otherwise, it returns false. This means that the function returns false if the argument is a string rdf:PlainLiteral data value. An empty input sequence is treated as a rdf:PlainLiteral data value consisting of the empty string, and accordingly on such input this function also returns false.

6 Acknowledgments

The RIF and OWL Working Groups made parallel efforts to support strings with associated language tags, as found in RDF. This specification is the outcome of a collaboration between the two groups, and it is based on the work on the datatypes rif:text and owl:internationalizedString.

In addition to members and chairs of both Working Groups, the editors would like to thank Addison Phillips, C. Michael Sperberg-McQueen, Eric Prud'hommeaux, Andy Seaborne, and Pat Hayes, along with other participants of the public-rdf-text mailing list, for their assistance in working out the details of this specification.

7 References

[RFC 2119]

RFC 2119: Key words for use in RFCs to Indicate Requirement Levels. Network Working Group, S. Bradner. Internet Best Current Practice,IETF, March 1997. [RFC 3986]1997, http://www.ietf.org/rfc/rfc2119.txt

[RFC 3986 -]

RFC 3986: Uniform Resource Identifier (URI): Generic Syntax. T. Berners-Lee, R. Fielding, and L. Masinter,Masinter. IETF, January 2005.2005, http://www.ietf.org/rfc/rfc3986.txt

[RFC 4647]

RFC 4647 - Matching of Language Tags. A. Phillips and M. Davis, IETF, September 2006.

[UNICODE]

The Unicode Standard. Unicode The Unicode Consortium, Version 5.1.0, ISBN 0-321-48091-0, as updated from time to time by the publication of new versions. (See http://www.unicode.org/unicode/standard/versions for the latest version and additional information on versions of the standard and of the Unicode Character Database)."

[ISO/IEC 10646]

ISO/IEC 10646-1:2000. Information technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 1: Architecture and Basic Multilingual Plane and ISO/IEC 10646-2:2001. Information technology - Universal Multiple-Octet Coded Character Set (UCS) - Part 2: Supplementary Planes, as, from time to time, amended, replaced by a new edition or expanded by the addition of new parts. [Geneva]: International Organization for Standardization. ISO (International Organization for Standardization).

[BCP 47]

BCP-47BCP 47 - Tags for Identifying Languages. A. Phillips,Phillips and M. Davis, eds.,eds. IETF, September 2006,2006. http://www.rfc-editor.org/rfc/bcp/bcp47.txt

. [RDF][RDF Concepts]

Resource Description Framework (RDF): Concepts and Abstract Syntax. Graham Klyne,Klyne and Jeremy J. Carroll, and Brian McBride, eds.,eds. W3C RecommendationRecommendation, 10 February 2004.2004, http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/. Latest version available as http://www.w3.org/TR/rdf-concepts/.

[RDF Semantics]

RDF Semantics. Patrick Hayes, ed., W3C Recommendation 2004Recommendation, 10 February 2004, http://www.w3.org/TR/2004/REC-rdf-mt-20040210/. Latest version available as http://www.w3.org/TR/rdf-mt/.

[SPARQL]

SPARQL Query Language for RDF. Eric Prud'hommeaux,Prud'hommeaux and Andy Seaborne, eds.,eds. W3C RecommendationRecommendation, 15 January 2008.2008, http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/. Latest version available as http://www.w3.org/TR/rdf-sparql-query/.

[XML]

Extensible Markup Language (XML) 1.0 (Fifth Edition). Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, Eve Maler, and François Yergeau, eds.,eds. W3C RecommendationRecommendation, 26 November 2008.2008, http://www.w3.org/TR/2008/REC-xml-20081126/. Latest version available as http://www.w3.org/TR/xml/.

[XML Namespaces]

Namespaces in XML 1.0 (Second Edition). Tim Bray, Dave Hollander, Andrew Layman, and Richard Tobin, eds.,eds. W3C RecommendationRecommendation, 16 August 2006.2006, http://www.w3.org/TR/2006/REC-xml-names-20060816/. Latest version available as http://www.w3.org/TR/REC-xml-names/.

[XML Schema Datatypes]

W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes. D.David Peterson, S.Shudi Gao, A.Ashok Malhotra, C. M. Sperberg-McQueen, H.and Henry S. Thompson, eds.,eds. W3C Working DraftCandidate Recommendation, 30 January 2009.April 2009, http://www.w3.org/TR/2009/CR-xmlschema11-2-20090430/. Latest version available as http://www.w3.org/TR/xmlschema11-2/.

[XPath20]

XML Path Language (XPath) 2.0. Anders Berglund, Scott Boag, Don Chamberlin, Mary F. Fernández, Michael Kay, Jonathan Robie, and Jérôme Siméon, eds. W3C Recommendation 23 January 2007.

[XPathFunc]

XQuery 1.0 and XPath 2.0 Functions and Operators. Ashok Malhotra, Jim Melton, and Norman Walsh, eds. W3C Recommendation 23 January 2007.

References/ref-bidi References/ref-xhtml References/ref-ruby

8 Changes Since Last Call

Since the last call draft of 21 April 2009, the following changes have been made:

• The name of the datatype was changed from rdf:text to rdf:PlainLiteral, to clarify the role and purpose of the datatype
• The names of the builtins and their namespace were changed to match the change in the name of the datatype
• The introduction and section 4 were rewritten to reframe this datatype as having a special relationship to RDF plain literals.
• The notion of an entailment relationship between plain literals and rdf:PlainLiteral typed literals was removed, since rdf:PlainLiterals are now more clearly understood to not occur in RDF graph syntaxes.
• The characters used to delimit pairs was changed, since problems were reported with &lang; and &rang; in some browsers