08:42:10 <gk> I have a concern: fully normalized presumes you know what
can be done with the string - e.g. is it XML or something else?

08:42:35 <bwm> uris:

08:43:04 <bwm> Graham - I'd like to be a record of the meeting -

08:43:18 <bwm> I'd like this to be a record fo the meeeting

08:43:31 <gk> * gk You plan to use this raw?

08:45:09 <bwm> question: what do we do with iri's

08:45:28 <bwm> three alternatives from email

08:45:43 <bwm> problem of losing information if reduce to us ascii

08:48:13 <bwm> wherever you use a uri you must allow an iri. when we
tidy a graph we are only allowed one node with a givin iri label. equality of
iri's is defined by algorithm c.

08:49:15 <gk> Suggestion: Comparison of URIs behaves as if all
URIs/IRIs are Unicode-normalized, but spec dosn't have to say that such
normalization MUST be performed; i.e. is comment on definition of URI string
equality

08:50:17 <bwm> if we have two iri's that are equal, then we just pick
one, which means they won't round trip precisely.

08:51:33 <bwm> next lang without parsetype literal

08:52:55 <gk> Consensus among developers who have implemented language
tagging of literals is that the language info is part of the resulting
literal

08:53:05 <bwm> thank you

08:53:34 <bwm> rdfcore heading for using pair to represent strings with
lang

08:53:52 <bwm> compare on lang component is case insensitive

08:54:09 <bwm> two issues: exact matching. ontology for
languages.

08:55:15 <gk> Proposed rules: language and string must be identical -
no lang does not match lang

08:55:21 <bwm> proposed rules for matching that strings don't match if
one literal has lang and the other does not

08:56:18 <gk> I18N want match more flexible, if one has lang and the
other doesn't, or if one is prefix of other.