Re: Fwd: [office-metadata] RDF datatypes

[Elias Torres <eliast@us.ibm.com>]

John Madden <john.madden@mac.com> wrote on 05/10/2007 01:10:25 PM:

> Begin forwarded message:
>
> From: John Madden <john.madden@mac.com>
> Date: May 10, 2007 1:09:21 PM EDT
> To: Svante Schubert <Svante.Schubert@Sun.COM>
> Subject: Re: [office-metadata] RDF datatypes
>
> I think Elias and Svante have this right now. I think the idea of
> generating additional blank nodes was just a thought experiment, and
> it clarified the issues.
>
> One thing Svante. I want to make sure the following would be allowed:
>
> [1] <ex:foo about="ex:solarSystem" property="numberOfPlanets" m:
> data-type="xsd:integer">9</ex:foo>

yes

>
> just as it would be allowed, but not be *required* to have:
>
> [2] <ex:foo about="ex:solarSystem" property="numberOfPlanets" m:
> data-type="xsd:integer" m:data-value="9">9</ex:foo>

yes

>
> or
>
> [3] <ex:foo about="ex:solarSystem" property="numberOfPlanets" m:
> data-type="xsd:integer" m:data-value="9">nine</ex:foo>

yes

>
> In other words, m:data-value is not *required*, and can be sensibly
> omitted if the string content child of the element in the DOM is a
> literal with a typed value in the domain of the datatype.

yes

>
> And in this case:
>
> [4] <ex:foo about="ex:solarSystem" property="numberOfPlanets" m:
> data-type="xsd:integer">baloney sandwich</ex:foo>
>
> then we have some kind of error condition that we deal with in some
> way (yet to be defined)--probably similar to the way we would deal with:

no. We don't throw an error. Our job is not of validating the world of
metadata.

What will you do when you have ex:myInteger? We simply generate the model,
it's up to the application to validate that. Since they are the ones who
understand the predicates and their range datatypes.

>
> [5] <ex:foo about="ex:solarSystem" property="numberOfPlanets" m:
> data-type="xsd:integer" m:data-value="baloney sandwich">9</ex:foo>
>

The same here.

-Elias