Present: Matt K., Stefan, Matt B., John N., Jamees, Martin

AGENDA: Follow up with Thorny Staples (Fedora Commons)

Bill P. sends the following in advance of the meeting: "If I may, I would like to register my interest in Fedora and asset actions and willingness to implement them and advocate / explain their use in MONK. This would be a low cost value to add. It's been done already for NCF and can be easily expanded with other collections and evolved with MONK."

Stefan: how invasive is Fedora? do we need to revise what we have, or is it a matter of developing in parallel

Martin: Bill P. thinks some aspects of MONK data store could be resolved in Fedora, especially summaries that are attached to chunks; for examples, aggregates of words and frequencies; this allows you to go to a look-up rather than pre-compiling on the fly

James: Fedora allows you to model your data as you like; if the relationships between MONK objects become fairly sophisticated, then capturing those relationship in Fedora might become trickier; Fedora works off of RDF

Big Question: Can Fedora become MONK's repository (for MONK objects or MONK chunks)?

Stefan: asset actions sound like they would allow MONK to communicate its collection behaviors to other projects

Next question: can we adopt asset actions without adopting the Fedora environment?

Martin: MONK lexicon; if this was modelled in a Fedora environment such

James: asset actions are a DLF Aquifer effort, not a Fedora effort

Matt B.: asset actions will be useful in terms of allowing our own tools to communicate across the interface

Stefan: are there specific, empirical things we can do with Fedora now?

Martin: Matt K. should talk to Bill P.