O'Reilly Network articles about this topic:
Emerging Technology Briefs: Identity
(Web Services DevCenter)
A brief look at the state of the emerging identity, membership, and preferences fabric for the Internet.
P2P Working Group Gets to Work
The P2P Working Group will meet May 30-31. Unlike previous meetings, this one will be about hard work, not politics.
P2P Working Group Meeting in May
The P2P Working Group is meeting May 30-31 in Santa Clara.
Interoperability, Not Standards
"Whatever else you think about, think about interoperability. Don't think about standards yet." Nothing Clay Shirky said at the O'Reilly P2P conference has netted him more flak than that statement. Read what he really meant.
Working Group Members Reject Intel Leadership
Members of the Intel-organized Peer-to-Peer Working Group yesterday voted for non-Intel leadership.
The Power of Metadata
The Web is a big, glorious mess of unstructured, unlabeled data of every possible flavor. Will P2P go down the same road? Now is the time to adopt some metadata standards that will allow P2P to become truly interoperable. This essay is an excerpt from Peer-To-Peer.
How the Peer-to-Peer Working Group Ought to Be Organized
Tim O'Reilly says that Intel squandered the opportunity to kick off a real working group process at its first meeting of the Peer-to-Peer working group.
Developers Explain - Why RSS 1.0?
O'Reilly Network publisher Dale Dougherty talks with some of the core developers behind the new spec proposal for RDF Site Summary (RSS 1.0) about the background behind RDF, the need for a standard, and what RSS enables
Other documents about this topic:
Below are other references available on the web for this topic. Since other sites may change their links, please if you find any that may need to be updated.
The Blocks Extensible Exchange Protocol (BEEP) Core
This Internet-Draft from the IETF's BEEP (Blocks Extensible Exchange Protocol) Working Group describes the details of BEEP's framing mechanism for the independent exchanging of messages between peers. BEEP messages can contain artibrary MIME content or structured text of some kind, such as an XML document. The draft also explains the key aspects of BEEP's "channels" and how they can be used to manage transport security, user authentication and data exchange. [Source: IETF]
RDF Site Summary (RSS) is a lightweight multipurpose extensible metadata description and syndication format. RSS is an XML application, conforms to the W3C's RDF Specification and is extensible via XML-namespace and/or RDF based modularization. [Source: RSS-DEV Working Group]
Magi P2P Collaboration Software For PDAs
Endeavors Technology's Magi P2P Collaboration Software For PDAs To Run Insignia's Industry-Leading Jeode Platform [Source: Endeavors Technology]
Mapping the BEEP Core onto TCP
This Internet-Draft from the IETF's BEEP (Blocks Extensible Exchange Protocol) Working Group describes how a BEEP session can be mapped to a single TCP connection. An explanation of how to send and receive messages reliably using TCP's SEND and RECEIVE calls is provided, along with a detailed description of the flow-control mechanism used to avoid starvation and deadlock during multi-channel BEEP sessions. [Source: IETF]
Instant Messaging / Presence Protocol Requirements
The goal of the IETF's Instant Messaging and Presence Protocol (IMPP) Working Group is to define a standard protocol so that independently developed instant messaging and/or presence applications can interoperate across the Internet. This informational RFC (2779) from the IMPP Working Group defines a minimal set of requirements for the group's deliverables. [Source: IETF]
What is RDF?
This article provides a bit of background about metadata in general, and then goes on to explain some specifics about RDF metadata, gives a detailed description of RDF's abstract data model and provides a number of examples of the structure and syntax of an RDF "statement". The article was originally published in 1998 by Tim Bray. Dan Brickley, chair of the W3C's RDF (Resource Description Framework) Interest Group, has updated the piece in order to reflect the various developments that have taken place over the last two years. [Source: XML.com]
Protozilla: pipes, protocols, and P2P in Mozilla
This white paper describes the nuts and bolts behind Protozilla, a browser add-on that makes it very easy to implement protocols in Mozilla (or Netscape 6.x). It is not a traditional browser plug-in, but may be described as a "socket adapter", like the kind that you may carry around with your laptop when you travel internationally. With Protozilla, implementing a new protocol becomes as easy as typing a one line URL prefix, or dragging-and-dropping a file. [Source: mozdev]
This W3C Member Submission from Akamai Technologies proposes a mechanism for assigning metadata to resources, or across groups of resources, based upon their Uniform Resource Identifier (URI) namespaces, in order to address an increasing need to manage metadata about resources. In the URISpace Model, an application can assign metadata to an entity based upon its URI namespace by building a tree of selectors that contains the metadata and describes the Uniform Resource Identifier namespace. This document describes the elements, describes tree structure and usage, shows how metadata may be represented, and defines ways to extend its functionality. [Source: W3C]