I'd add to Scott's excellent advice the suggestion that if you decide to use your own defined relationships, consider using the Enhanced Content Models ontology-validation functionality:
http://sourceforge.net/apps/mediawiki/ecm/index.php?title=Ontology_Language to govern your new relationships inside your repository. --- A. Soroka Online Library Environment the University of Virginia Library On May 17, 2011, at 9:16 AM, Scott Prater wrote: > Hello, Walker -- > > It depends on how you plan to use the RDF relationships. Will you be > doing queries against the resource index to retrieve objects that have > this relationship? If so, will you need to distinguish, either now or > in the future, between objects that are part of a donor relationship and > other objects with a "hasRelation" relationship? If the answer to these > question is "yes", then you'll want to use a different, more exact > relationship. > > There's nothing to prevent you from using relationships from different > RDF schemas in your triples, or even making up your own (namespaced) > relationships yourself and using those; in fact, it's a quite common > practice among Fedora maintainers. > > Here's an example of a homegrown RDF schema we wrote for some homegrown > relationships: > > http://digital.library.wisc.edu/1711.dl/rdf/1.0/relations > > -- Scott > > > > On 05/14/2011 02:04 PM, Walker Sampson wrote: >> Hi all, >> >> I have a question regarding the best use of Fedora relationship ontology. I >> need to designate a 'donor' relationship between two Fedora objects (an item >> and a donator). I haven't found namespaces with this specific property >> detailed, but a generic 'hasRelation' property would also suffice. >> >> To that end, would it be advisable to use the primitive property >> 'fedoraRelationship' to note such a relation? I understand that all the more >> descriptive properties are a subtype of this one, but would it work to >> simply have this property note the relation between an item and donator as a >> basic object-to-object relation? >> >> Thank you, >> Walker >> >> >> >> >> ------------------------------------------------------------------------------ >> Achieve unprecedented app performance and reliability >> What every C/C++ and Fortran developer should know. >> Learn how Intel has extended the reach of its next-generation tools >> to help boost performance applications - inlcuding clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> >> >> >> _______________________________________________ >> Fedora-commons-users mailing list >> Fedora-commons-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > > > -- > Scott Prater > Library, Instructional, and Research Applications (LIRA) > Division of Information Technology (DoIT) > University of Wisconsin - Madison > pra...@wisc.edu > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > Fedora-commons-users mailing list > Fedora-commons-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
