|
|
|
|
|
by sander
5148 days ago
|
|
We basically have 2 approaches to this problem. When people have existing data with some structure, they can easily convert this into a semantic Silk site. This can be done using various importer tools (such as our CSV importer) and via the read/write API. When people are creating new content, we're trying to make it as easy as possible to add semantics/tags. It's as easy as making your text bold and we try to provide instant value to users who tag their content, thereby encouraging them to keep doing so. Some things we do are:
- converting currencies
- showing how long ago a date was
- displaying a map for locations
- showing how data relates to other data (tagging the age of a person, will show a list of how old other people in the site are) So, if you have unstructured data and are looking for one quick answer, Silk may not be the right tool to use. When the data has some structure already, you can easily convert it into a Silk site and then enjoy some Silk magic. But ideally, you use Silk to make some specific content available in a structured manner, so you can use it for a longer period of time. |
|
Do you do any sort of history-based analysis? E.g. solving "I just imported this, which I tagged with a,b,c from locations x,y,z, now I want to import this, that has d,e,f also from positions x,y,z" - I guess Wikipedias info boxes would be a typical example of that kind of semi-structured data. Or does that require setting up an import channel yourself?