Re: Coming to consensus on the default datatype

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben,

thanks a lot for this summary. I could follow everything you said, and
usually agree, until the very end...:-( Where I was lost for a moment.
You list a bunch of use cases:

[snip]
> 
> So here's a proposal for discussion, which is only a slight tweak on the
> approach already mentioned by Mark and Steven, which is meant to make
> for easy defaults and reasonably easy override in both directions with DRY.
> 
> 1) Ian's use case:
> 
> <http://example.com/doc> dc:title "RDF or Bust" .
> 
> ========
> <h1 property="dc:title">RDF or Bust</h1>
> ========
> 
> 2) Mark's use case:
> 
> <http://example.com/doc> dc:title "E=mc<sup>2</sup>"^^rdf:XMLLiteral .
> 
> ========
> <h1 property="dc:title">E=mc<sup>2</sup></h1>
> ========
> 
> 3) Overriding the type when the markup is for presentation only:
> 
> <http://example.com/doc> dc:title "This guy is truly intelligent" .
> 
> ========
> <h1 property="dc:title" datatype="plain">
>    This guy is <em>truly</em> intelligent
> </h1>
> ========
> 
> 4) Overriding the type to stay consistent with other XMLLiteral data stores:
> 
> <http://example.com/doc> dc:title "E equals mc squared"^^rdf:XMLLiteral .
> 
> ========
> <h1 property="dc:title" datatype="rdf:XMLLiteral">
>    E equals mc squared
> </h1>
> ========
> 
> 
> I think we're pretty close to consensus on something like what Mark and
> Steven proposed, possibly with the above twist. 

But I am not sure from the text what the proposal is!:-( But let me try
to articulate it, maybe I get it right:

- - By default:
 - if the content contains xml elements of any kind, the literal is of
XMLLiteral
 - if the content does not contain any elements of any kind, the literal
is plain
- - You introduce (beyond the datatypes inherited from RDF/XML Schema, eg,
XMLLiteral) an extra value for the datatype that is 'plain', with the
obvious meaning.

I can very well live with that. The only mini-mini question is whether
we would have to have a separate namespace for this value, ie, it should
be 'rdfs:plain' instead of 'plain'.

Maybe we could also add the extra twist, ie, that if one uses
rdf:XMLLiteral, that would switch off, so to say, any RDFa processing in
the literal, too. Ie, that could solve Ian's puzzle; his

<div about="">
    <h2 property="dc:title">
      E = mc<sup property="rdf:value">2</sup>: The Most Urgent Problem
of Our Time
    </h2>
</div>

would have to use:

<div about="">
    <h2 property="dc:title" datatype="rdf:XMLLiteral">
      E = mc<sup property="rdf:value">2</sup>: The Most Urgent Problem
of Our Time
    </h2>
</div>

to generate the triple he needs...

Thanks

Ivan

- --

Ivan Herman, W3C Semantic Web Activity Lead
URL: http://www.w3.org/People/Ivan/
PGP Key: http://www.cwi.nl/%7Eivan/AboutMe/pgpkey.html
FOAF: http://www.ivan-herman.net/foaf.rdf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGAP7kdR3hQzQ/Gj0RAmOFAJ4u4oqzRlO24V+ktsIJJ/0SoDWl4gCaA10F
EtWd/wcgxb7uNT68IvC/lK4=
=6Vdk
-----END PGP SIGNATURE-----

Received on Wednesday, 21 March 2007 09:46:36 UTC