User: Zhimin Wang | User: Chinua Iloabachie | User: Paul J. Morris | User: David Lowery | User:
- Zhimin: Has been working on documentation of design. Network, notification, and knowledge base now have design documentation. Web client is in progress. Evaluation of platform also in progress. We examined and discussed elements of this Report:_Evaluation_of_FP_prototype_technologies
- David: Has been documenting evaluation of XML binding technologies, and has added these to the reports. Continuing to work with JiBX, and has been marshaling Specify6 agents to xml, with a path from the MySQL database, Hibernate, JiBX, and on to an xml document. Updated documentation, particularly configuration and deployment. We discussed agents involved in transactions and privacy/data availability issues this raises for the network.
- Chinua: Working on documenting web client code. Exploring richfaces solutions to user interface design suggestions from James in review of current web annotations UI - issue is navigation mechanism for going from the current synthetic view of an annotated record to the particular annotations that might be of interest to a particular user.
- Paul: James and Paul had a long conversation last week with Tim Roberstson at GBIF about IPT, FP, and annotations. GBIF is very interested in discussion of annotation standards. Tim has sent a data use agreement to James, and when that gets back to him, GBIF can provide us a copy of the cache to use with a deployment of the FP web interface.
The computer science literature talks about integration systems composed of global schema, source schema, mapping, and constraint on global schema (G,S,M,Cg). The general mapping formula is: ∀x⃗∊SΨ(x)⟶∃y⃗∊gΦ(y,x) The transformation from a set of attributes in S to a set of attributes in G can be expressed a constraint system with an understood formula. There is a published algorithm from IBM to carry this out which has proved to be correct, IBM had been prototyping this under the name CLIO around 2004. General case has lots of complexity, we need to better understand the specific use cases for our domain to understand what specifics to implement.