LSID: What's still needed to make it work within the semantic web?

We had some very productive discussions on the value of the LSID specification at the workshop in October, and many of us would like to see it reach a functional conclusion. Much of the discussion was around what still needs to be done with the specification, so that LSID's become a beneficial and practical element of the life science community. I would like to suggest those interested in seeing the LSID specification come to completion, to participate in this thread, and try and define some critical next steps for its success in being adopted by most data sources. 

I would also recommend people to re-read the 3 position papers on LSID from last October's workshop: http://www.w3.org/2004/07/swls-agenda.html . Steve Chervitz's paper from Affymetrix has some very useful insights in it that I think many would appreciate. 

To quickly review, LSID offers both a unique identifier model for authoritative life science data, and a mechanism by which they can be resolved to actual (unmutable) data bytes and meta-data (mutable). Some lingering quaestions include: 

* What metadata accessible through LSID should be standardized; this may be more about general info-descriptive semantics like Dublin Core and RSS, than biological or chem semantics.  

* A precise way to handle versioning, derivation, some other relationship types for provenance 

* Are URN-aware resolvers an acceptable means for data retrieval for all members of the life science community? Are there any alternatives that are simpler? 

* Guidelines for encoding data for common bioinformatics data types in LSID; are we all clear what is data and what is metadata? Would this include all kinds of RDF graphs that relate to the original data item? Do we need best practices on utilizing common ontologies such as GO within a data entry? 

* How to specify Dynamic data (latest version) effectively (minimal http calls of LSIDs) 

I hope other members of the LSID specification are able to participate on this thread, to help clarify the issues, and identify where most value can be gained. 

Eric