>> Can anybody give a short comment on the use of facets:facets in >> http://simile.mit.edu/2006/01/ontologies/fresnel-facets?
Of course also the long answer was very appreciated. Thank you very much for clarifying this! So putting a property into the list makes it a facet. I don't know why I questioned that, of course that's the use of the list. However then, the members of the list are not even restricted to rdf:Propertys at all, are they? That's what I first had in mind you wanted to do, but I think I can live without this restriction, cause the application can care for this. Jan >> >> Do I have to make my rdf:Propertys be a :Facet to allow them >> beeing in the List? > > An appropriate inference from the presence of a resource in a facet list > is that it is of type :Facet. The general approach to RDF is to treat > it as an open world: if something is asserted to be black and also > asserted to be white, a proper resolution is that it is both, not that > one of the assertions is wrong. Likewise, because a resource is in the > facet list, the proper resolution is that it is in fact a facet, not > that it is misplaced or not typed correctly. > >> If yes, is it the right way to assign those properties :Facet as an >> additional type? > > The above description is actually the way the Fresnel engine operates - > you don't need to assert that something is a :Lens, just that it applies > to a particular type or instance (or other valid lens selector). > > So the short answer is no, you don't need to do anything special > regarding the :Facet type. > > -- > Ryan Lee [email hidden] > MIT CSAIL Research Staff http://simile.mit.edu/ > http://people.csail.mit.edu/ryanlee/ > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
