Following up on Mike Park's messaging thread, I'd like to also suggest the addition of relationship-level notifications (in addition to the API-M level messages).
The drawback of API-M messages is capturing updates to the RELS-EXT/INT when they are modified by modifiyDatastream rather than the add/purgeRelationship methods. In some circumstances, it isn't even possible to reconstruct (through set operations or otherwise) what changes took place (as when the versioning is disabled). At the most basic level, this could support (or, at least simplify) maintaining external triplestores or similar. It seems like this isn't too difficult given the current setup, but probably results in additional mass purge + recreate operations. My immediate use case is domain-specific implications for specific relationships (like collection membership, content model assertions, or even state-based triples) that could trigger workflow processes (whenever an object is added to collection X, notify A; whenever an object asserts it is an archival video, start an encoding process to create a new proxy copy; etc) . Thoughts? To me, it seems a little too different than API-based messages to be an easy addition, but it also seems like it'd really help streamline some applications, especially as more people start developing workflow processes around Fedora. Thanks, Chris Beer Web Developer WGBH Interactive ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
