...
- Put agenda on Fedora Community (seems OK for everyone)
- Working down the list of use cases
- Stefano - Content Model
- Content modeling
- Have a model resource
- Use content model (with parameters) to formulate the form of the data returned
- Use to make/handle derivatives, metadata extraction, feature extraction
- Not hard code content model but use the model to guide processes
- Manage types and control relationships and other controls (cardinality, unique IDs etc.)
- Manage inheritance of modeled features
- Andrew, draw out common patterns. Where is the starting point?
- Andrew, implies complex step, multiple components ingest, Sparql, converters, validation
- Aaron, described possible common elements
- Stefano, model concentrates on the wiring dispatching to the right tool
- Aaron, we need a clear scenario that illustrates an example how things should work
- Stefano, started an implementation but the scope was too big
- Aaron, an example may use a set of object paths
- Stefano - Access Controls
- Would cover more components such as the triple-store with a comprehensive access controls
- Ruth - Federated Search + more
- Researchers want to be able to search over many repositories
- OpenSearch informs this
- Do layers of search
- Classified searches for the kind of data (discipline)
- Elliot - more than Federated Search (what is amenable to a kind of search)
- Elliot - How should we proceed
- Aaron - Extract common patterns
- Stephano - Use a new section to describe common patterns
- Andrew - Hoping that we would have more understanding of use cases for discussion and identifying patterns
- Elliot - Can we try to get the Wiki page for patterns in one week so we can discuss in two weeks (Wiki deadline - Friday Sep 4)
- Elliot - How can we communicate especially questions? Use comments on page?
- Tim - Wiki page better because it too easy to lose track on email