Hi Steve, > (a) when ingesting content model objects, should we enforce a RELS-EXT > assertion to a valid content model for content model objects? or > (b) should we create a Resource Index triple identifying the > fedora-system:ContentModel-3.0 as a default for content model objects when > none is specified in RELS-EXT?
I think a) would be better, as b) would be too surprising for most people. The challenge, as you noted, is how to infer that an object was intended to be a cmodel if it doesn't correctly indicate it via the hasModel relationship. Two obvious things to check are the existanence of the DS_COMPOSITE_MODEL datastream and the existance of the hasService relation. If either is present, there is an overwhelming probability that the object was intended to be a content model object. > (c) should we stop CMA features working (eg the dissemination execution) if > the object identified as the content model does not itself identify through > RELS-EXT that it is a content model object? If a) were already implemented (particularly if we said that a hasService relationship means a hasModel->FedoraContentModel-3.0 relationship must also exist), I'm not sure c) would add any value...just code. But I haven't had my coffee yet...I might be missing something. - Chris ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
