4 ms·
You're right: content is on our servers so we can build up all the indexes to allow for fast searching and querying. Not sure why that would be a problem thoug
by salar 15y ago
You're right: content is on our servers so we can build up all the indexes to allow for fast searching and querying.
Not sure why that would be a problem though. We don't intend to lock-in peoples content and we'll provide a REST based read/write API – so you can get the content in and out whenever you want.
- Ixiaus 15y agoI think what you're doing is super cool and as long as you do indeed provide an easy route to getting the data off the servers then I don't see a problem at all. Is this meant to be a freemium model? Or is it going to be a paid service? How do you go and use this in a website though? That's another facet of the semantic web that I think needs to be addressed too - content is great but if I have to export it from your servers then stick it into my website, that could get to be a pain. Is Silk maybe going after a Semantic Cloud sort of model? I think that would not only be tenable but a really smart move. I would use a Semantic Cloud service.
- salar 15y agoYes, it's going to be freemium like. We'll be announcing various stuff around the actual product really soon, but the idea is that Silk could become your website, in the same way that Tumblr works as a website for a lot of people. I love the idea of a "semantic cloud", it's exactly what we're going for actually. I'm going to use that if you don't mind :-)