Over the past half-month, the primary issues have been Storage, CMS, and Web Services, along with Authentication, Citations, and Quality. *Storage: Of primary concern is how the data will be stored, and so far SQL, RDF, and XML have been mentioned. *CMS: The various CMS solutions can be divided up by primary method of storage, with Drupal using SQL, TOPAZ/Fedora.info and Kowari using RDF, and GWT and Lenya using XML. *Web Services: Providing open access and giving control to the community in general require services such as comments/patents syndication, distributed rating, distributed submission, and distributed search. *Citations: Besides the ubiquitous URL as a means of citation, DOI might also be considered, since it is used by many (prominent) (scientific) journals. *Authentication: Authentication is often performed via HTTP POST, and this method can be used both on an http form and in the web services. *Quality: Rating by voting, as used on Slashdot and Digg and Reddit, is a convenient albeit basic way of determining quality, falling midway between the Google method (of using link analysis algorithms to determine quality) and the Wikipedia method (of allowing content maintainers to determine quality). One item that has not been discussed but rather implied is a need to access data (comments, patents, ratings, users, searches) by URL, and the various CMS solutions should be seen in this light. XPath is the W3C standard here, but any means of reference will work as long as it can be identified and parsed by a computer. A final issue that has been indirectly asked and not answered is whether it is reasonable and feasible for Peer2Patent to scale in the future to handle all patent jurisdictions. In this case, Peer2Patent would become the definitive online source for patent information, a la Wikipedia, although other sites may become the popular way to accessing this information. Peace, Brandon
