> I have checked the Fedora code. There are 32 usages of the reference > Constants.MODEL.HAS_MODEL, to get the content models of a object. To me, > this feels like something that should be collected in a general method, > like getContentModels(pid) or the like.
If I remember correctly, that was the original intent, but due to time constraints in releasing Fedora 3.0 the Constants.MODEL.HAS_MODEL relation was used directly wherever it was needed. As Chris alluded to earlier, I believe the original approach, was a method on DigitalObject or DOReader (I don't remember which). Of course, these are just internal interfaces in the server code - we should also consider the possibility of adding a 'models' method on a system SDef so that this information is accessible by the public APIs. When we implemented the CMA, we introduced some tables Fedora's registry database for mapping SDefs to SDeps for a given CModel (the ModelDeploymentMap table) specifically to avoid having to require the RI. So far, the conventional wisdom has been to avoid requiring the RI for core functionality. This may change after some debate, but at least for now, creating internal tables in the registry database to support fast inheritance-related lookups would be a consistent with existing implementation patterns. -Aaron ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
