- From: Amy G <amy@rhiaro.co.uk>
- Date: Sun, 18 Oct 2015 15:52:39 -0400
- To: Sarven Capadisli <info@csarven.ca>
- Cc: "public-socialweb@w3.org" <public-socialweb@w3.org>
Received on Sunday, 18 October 2015 19:53:26 UTC
> > The design of the Social API doesn't need to rely on any particular > vocabulary. People will use whatever vocabulary they deem to be appropriate > to describe their own "social" data. The Social API will merely enable the > data to be passed. The challenge for the Social API is to lay down some > form of a common denominator of the social API-like things that's needed. ... > . We are certainly not covering all aspects of the social web, neither > should we presume to or force it as such via a specific vocabulary. > +1 I think AS2 as a SHOULD is more useful than leaving it completely open, to encourage people who have no existing preferences to converge on something, but we shouldn't be forcing that on people if it doesn't match the shape of the social data they want to pass around.
Received on Sunday, 18 October 2015 19:53:26 UTC