[foaf-protocols] new WebID Charter draft

peter williams home_pw at msn.com
Thu Dec 16 00:17:57 CET 2010

"1.2 Out of Scope 
Making the protocol complex by attempting to solve all problems. "

Enumerate the classes of things that are out of scope: e.g.

Interoperability considerations with operational or historical https
Worrying about the implications for export grade ciphers
Mappings onto API frameworks
Tracking IETF TLS I-Ds (focus only on RFCs)
Consideration of must/should/ topics, for such as FOAF document notations
Applicability Statements
Coherency analyses with web architecture 

The above are not hard to formulate. They are basically what IETF/IESG  does
for a standards track efforts, that we don't do in an incubation exercise.

-----Original Message-----
From: foaf-protocols-bounces at lists.foaf-project.org
[mailto:foaf-protocols-bounces at lists.foaf-project.org] On Behalf Of Henry
Sent: Wednesday, December 15, 2010 2:18 PM
To: foaf-protocols at lists.foaf-project.org
Subject: [foaf-protocols] new WebID Charter draft

So I tried to apply the suggestions put forward by everyone on this list.
Here they are. 


With github changes here


As previously, Feedback is welcome.
 We can then start the process tomorrow hopefully.


Social Web Architect

foaf-protocols mailing list
foaf-protocols at lists.foaf-project.org

More information about the foaf-protocols mailing list