Andrew Miller wrote: > David Nickerson wrote: >> Just to note that the page for the website has been ready for a while >> now, it is only the programme which is not finalised and can't be until >> we know who can make it....and we are running out of time to promote the >> event... >> > Thanks for the correction. > > I have put an errata note after the relevant part of the minutes > explaining this.
Thanks Andrew. I have just adjusted your errata a bit to reflect what I meant. The web page for the workshop is ready to be made public its just waiting on an appropriate location to be made available on cellml.org. The programme is still a work in progress and it is hoped that once invitations have been sent and replies received we'll get that finalised pretty quick and make it available. >> Finally, just wondering if we could get an update (to the >> cellml-dissussion list?) on the work Tommy is doing with metadata and >> the repository and how it ties in to the CellML API? >> > The CellML API doesn't have a metadata API, but I hope that Tommy's work > can at least give us a structure for the API (unfortunately Tommy's work > is in Python, to match with Zope, which isn't a very good match for the > rest of the CellML API). Other than that, there is no relationship, > because Tommy's work uses Python RDF APIs. What I was really after is whether Tommy is taking this chance in re-writing the metadata handling in the model repository to actually integrate the CellML API into the model repository product (PMR). ie, using the API to fetch the RDF from a model and then ensuring any changes in the metadata via the web interface are reflected in the actual CellML model. Although is there any interface(s) in the API for changing the RDF contained in a model? I would imagine that at the least this would result in a clearer definition of the repository requirements for the high level metadata interface Matt proposed a while ago - things like get/set publication(s), authors, modification history, etc... From what you are describing this is almost what Tommy is working on, but doing it in Python code independent of the CellML API. The Python code may then be taken and incorporated into the API to provide the same functionality in a more generally usable package...have I got that right? _______________________________________________ cellml-discussion mailing list [email protected] http://www.cellml.org/mailman/listinfo/cellml-discussion
