Hi Richard, Functionally, it's perfectly legal to have a content model object that doesn't refer to any SDefs. You can also have a content model object that doesn't declare any required datastreams. In this way, it is possible to have an empty content model that acts as a sort of "marker".
Note that you could also use an arbitrary property to accomplish the same goal. For example, on your parent objects, put a "hydra:isParent" = "true" relation in RELS-EXT. Client applications could discover that as easily "fedora:hasModel" = "info:fedora/demo:someHydraModelIndicatingParenthood". I would use the empty content model approach if there's a chance that the parents would ever have special behavior or datastream requirements in Fedora. If not, then I think defining your own boolean property would be the more straightforward approach. - Chris On Fri, Sep 25, 2009 at 12:24 PM, Richard Green <[email protected]> wrote: > Chris and others, > > The Hydra team have decided that normal Hydra objects will all subscribe to > the same content model which defines metadata datastreams. This is actually > adequate for the parent of an aggregation object – it does not also need to > subscribe to another content model to define any content-bearing > datastreams. > > However, it would be useful to have aggregation parents subscribe to a > content model ‘genericAggregationParent’ simply so that they could be > identified (perhaps, say, to trigger a specific behaviour in the search and > discovery interface). Is there any harm in defining such a content model > and referencing a datastream already declared in the common metadata model? > Is it possible/better to declare a content model referencing *no* > datastreams (what do you do about the SDef reference)? Or? > > Advice would be welcome! > > Best > Richard ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
