I agree with you. I actually think that there is not a single property in the Nepomuk ontologies that could not have a typed literal range (well, except for the ones that have non-literal ranges of course). But changing that now could break backwards compatibility without any real gain. At least I cannot think of any practical advantage to fixing the ranges.
Cheers, Sebastian On 04/20/2010 04:20 PM, Evstifeev Roman wrote: > Looking at those two properties: > 1) nfo:fileName > rdfs:range <http://www.w3.org/2001/XMLSchema#string> > 2) nao:description > rdfs:range <http://www.w3.org/2000/01/rdf-schema#Literal> > > am i right, that: > nfo:fileName here have range of typed RDF literal of type xsd:string > nao:description have range of some RDF literal (typed or plain) > > and second: > why range of those properties are different? It seems to me, that > nao:description only will ever contain a string too, and range of any RDF > lieral is useless here. (for ex. using xsd:integer as a description is weird) > _______________________________________________ > Nepomuk mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/nepomuk > _______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
