Harry Halpin wrote: > In detail, these are the only parts of OWL used are cardinality > constraints [1], while in the original vCard/RDF[2] it was implied that > not having these sort of constraints was not a bug, but a feature: > > So, do we need these? Or do they complicate things? If we have > cardinality constraints they allow us "round-tripping" without loss of > data, but if don't have them them people can have much more flexible > names and organizations and the like, and keep vCard in RDF/S as opposed > to OWL. > Why not create two ontologies, with the second one (with cardinality constraints) further constraining the first one (those without)? So, when people use the vCard, they can use the rdfs:isDefinedBy to suggest to an RDF engine if additional constraints should be retrieved or not? I am a firm believer of ontology modularization. I think we should avoid build large monolithic ontology at all cost. We should build ontologies on small scales. Doing so will help users to pick and mix also it will help ontology's graceful evolution. XiaoshuReceived on Tuesday, 6 February 2007 04:39:20 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:22:45 GMT