jrweave/open-graph-protocol — comment on commit 455a2141ec3fab4096d75def3a9be30a3726eb4d
File:  line 0
By jrweave:

ogc:string has a strange requirement that the lexical representation be UTF-8 encoded, but really, the encoding should be independent of the lexical space. For example, "1" is in the lexical space of xsd:integer, but whether it is encoded in ASCII, UTF-8, UTF-16, UTF-32, etc., doesn't really matter. Thus, a datatype (in defining its lexical space) shouldn't really mind itself with the encoding. xsd:string makes no requirements on the encoding, but only requires that each character have a corresponding Unicode codepoint ( http://www.w3.org/TR/xmlschema-2/#string ).

That may sound a bit too theoretical, but it has major implications in practice, too. If an ogc:string can only be sequences of UTF-8 encoded characters, how can anyone specify (for example) an og:title if the encoding of the entire page is something other than UTF-8 (or ASCII)?

So I think the problem is with the definition of ogc:string, prompting me to ask, why the restriction to UTF-8?