On Fri, Apr 16, 2010 at 9:21 PM, dhavaln wrote:
> but this will create islands of information and information retrieval
> based
> on annotations will be difficult for other applications.
> i.e. amazon.com:book-rating{isbn:34345434, rating: 5}
>
> it should be easier for other applications to find
We definitely want to have documents on dev.twitter.com with best practices
and guildelines. That will be key. We're looking for everyone to help devise
the rules of the road.
On Fri, Apr 16, 2010 at 11:59 AM, gabriele renzi wrote:
> On Fri, Apr 16, 2010 at 8:51 PM, Marcel Molina wrote:
> > Mor
On Fri, Apr 16, 2010 at 8:51 PM, Marcel Molina wrote:
> More namespace nesting would of course increase people's ability to
> taxonomize. It's a splippery slope though and we are trying to balance
> expressiveness with simplicity. Providing for arbitrarily nested namespaces
> increases complexity
More namespace nesting would of course increase people's ability to
taxonomize. It's a splippery slope though and we are trying to balance
expressiveness with simplicity. Providing for arbitrarily nested namespaces
increases complexity considerably both from an implementation perspective
and a comp
