...
- In NSDL Wiki
- Move to FR30 to reduce pain points.
- OAIprovider does not have an understanding of NSDL Information model
- Makes it difficult to find related items
- Views are inconsistent
- Resource -> Aggregator -> Aggregator -> Aggregator path can be traversed, queried, or be a service itself
- Eddie - Repository should know its own structure without depending on client
- Chris - Also like an inferencing problem
- Both Content Model and SDef represent kinds of "typeiness"
- For access this is easier to see but what about create/ingest/write
- Could we generate Client code?
- What REST style is most effective for Fedora?
- Thought Experiment
Rick - Plone & CMS
- Plone - CMS in Python
- Collections are captured searches
- Links (except the built-in generic isLinkedTo) are user defined strings
- Content Modeler widely used.
- Active content display server
...