Semantic Web

Data is data, what you want to do is label the data as what it is, an opinion or a rating. A "fact" I suppose which could be inferred from such data would be that most people had x subjective opinion about said topic. source

Programming the Semantic Web by Toby Segaran just came out recently. It's a good combo of theoretical and practical advice on the subject. He's a great teacher and the book is appropriate for all audiences. source

I'm currently working on some really small projects in this area and I "mostly" use RDF there, although for parsing purposes I use a simple URI-registry in order to avoid cycles in the data structure itself. Although, I have to say that I'm still in the conceptual stage of these projects. In the end I rely mostly on 3rd-party storage backends like Jena, rdflib et al. source

Specifically, semantic social networking means embedding the actual social relationships within the page markup. The standard format for doing this as defined by microformats is XFN , XHTML Friends Network. In regards to the semantic web in general, microformats should be the go-to guide for defining embedded semantic content. source

I find that the biggest headache about frames is that a frame-state cannot be represented by a URL, and hence it cannot be bookmarked, shared, and so on. I use frames sparingly, and then, only in cases where it either makes no sense to create a frame-state bookmark or I specifically want to disallow treating a frame-state as a unit. For instance, I might put an interactive component in an iframe, if it should be reset to an origin state when the page is initially loaded. It seems to me that frames were created to allow plain-ol' HTML authors the opportunity to reuse their code without having to understand SHTML, CGI, application servers, or what have you. As a solution to this problem, frames most definitely suck. source