RE: Proposed N-Triples changes for datatypes & (untidy) literals

Sorry Dave I had not read your message before sending my later message which
should have referred to it.

I'll just not where my position (expressed as my choices in my message)
agrees or differs from yours.

>
>
> Adding datatyped literals
> =========================
> Change 1
>
> FROM
> literal ::= langstring | xmlString
> TO
> literal ::= langstring | xmlString | datatypeString
>
>
> Change 2
>
> ADD
> datatypeString ::= uriref '"' string '"'
>
> OR
>
> Change 3 (if datatypes can have language)
>
> ADD
> datatypeString ::= uriref '"' string '"' ( '-' language )?


Change 3 not change 2.
(Note xmlString is not datatyped).

>
>
> Adding untidy literals (and bnodes are required)
> ================================================
>
> Change 4
>
> FROM
> langString ::= '"' string '"' ( '-' language )?
> TO
> langString ::= ( nodeID )* '"' string '"' ( '-' language )?

NodeID not necessary. Literal node is untidy and unreferencable.

>
>
> Change 5
>
> FROM
> xmlString ::= 'xml' langString
> TO
> xmlString ::= ( nodeID )* 'xml' langString

Ditto.
>
>
> Restricting xml language to 1+ characters
> =========================================
>
> No change needed, existing definition is correct:
>
> language  ::=  ( character - ( '.' | ws  ) )+
>   and containing any allowed xml:lang content as defined in
>  http://www.w3.org/TR/REC-xml#sec-lang-tag
>
Agreed.


Jeremy

Received on Monday, 23 September 2002 04:03:34 UTC