Jon put together a scoping statement, list of use cases (1 from A wead) and technologies used with comments from others.
Mike read through the scoping statement for consensus
Do we extend the scope of the document to include vocabularies and conceptual models?
Focus is on technical work on RDF, there is another potential strand of work on the vocabularies used, conceptual model, URI design - focus less technical and more on the library side of things. Some in the community like UCSD, Royal library and Oxford have done work on RDF conceptual models.
Capture and point to existing models
Taking on a common model implementation might be ambitious - too many discussions on modelling.
Underling technology to be model agnostic is good. It would be useful to take the technical implementation and prove it doesn't have any constraints on the models used.
Rather than common models, we could come up with a set of reference models that users can leverage. For example the scholar sphere data model or UCSD data model or Denmark's data model
Recipes for how one can extend a common model without losing on interoperability and extend on complexity would be useful
Summary (by Mike)
Solicit and gather examples of data models from folks using RDF in Hydra
Have documenattion for aiding folks with data models
Mike to add notes on a wiki page about data models (DONE, 2/25)