Remove ads
Fluidinfo, formerly named FluidDB until early 2011, is an online cloud data store based on an attribute-value centric data model.[1] Fluidinfo is written in Python and characterized by a publicly writeable schema-less database that provides a query language, a fine-grained permissions model and promotes data sharing, both publicly and in groups.[2] The lack of an underlying RDBMS structure may classify Fluidinfo as a type of publicly writeable "collective database".[3][4]
| Original author(s) | Terry Jones, Esteve Fernandez |
|---|---|
| Developer(s) | Fluidinfo |
| Initial release | 2009 |
| Written in | Python, Twisted, PostgreSQL, Thrift, AMQP, Lucene |
| Available in | English |
| Website | fluidinfo |
Remove ads
Few data stores are available with the intent to provide public write-access, except in narrow contexts. Two examples of shareable data stores operating in specific contexts are del.icio.us (shareable bookmarks) and Twitter (micro-blogging service). Fluidinfo offers a generalized shareable data store, where potentially any piece or type of information can be shared with anybody else, if desired, striving for a balance between individual, group and communal data ownership. Author and blogger Robert Scoble described Fluidinfo as a "database that acts like a wiki".[5]
Fluidinfo emphasizes three aspects that make it unique among existing public data stores:
- Data model
- Query language
- Permissions
Data model
The data model aims to be as flexible as possible, permitting a wide range of information to be stored in Fluidinfo. The fundamental difference between attribute-value stores (along the lines of EAV schemas) and traditional RDBMS is the lack of a highly defined top-down structure. The essence of Fluidinfo consists of arbitrary objects, which can be considered points in a data space to which tags may be attached. Objects have no owners, similar to concepts in the "real" world. Tags are initially controlled by the user/application who creates them and can be attached to objects, in a fashion reminiscent of how humans use their minds to create and associate information with physical objects or concepts. One of the underlying motivations of Fluidinfo is to make working with information more natural.[6] Anyone can attach tags to any data object, but only people with the right roles can see and search these tags.[7]
Query language
The query language was designed to perform complex queries in as simple a manner as possible.[8] The syntax is superficially reminiscent of information retrieval query languages such as CQL which are characterized as less complicated than traditional database query languages such as SQL. The query language always return object identifiers based on tag values, using the predicates below:[9]
- Numeric: To find objects based on the numeric value of tags; e.g.
tim/rating > 5 - Textual: To find objects based on text matching of their tag values; e.g.
sally/opinion matches fantastic - Presence: Use has to request objects that have a given tag; e.g.
has sally/opinion - Set contents: A tag on an object can hold a set of strings. For example, a tag called
mary/product-reviews/keywordsmight be on an object with a value of[ "cool", "kids", "adventure" ]. Thecontainsoperator can be used to select objects with a matching value. The querymary/product-reviews/keywords contains "kids"would match the object in this example. - Exclusion: You can exclude objects with the
exceptkeyword. For example,has nytimes.com/appeared except has james/seen. Theexceptoperator performs a set difference. - Logic: Query components can be combined with
andandor. For example,has sara/rating and tim/rating > 5. - Grouping: Parentheses can be used to group query components. For example,
has sara/rating and (tim/rating > 5 or mike/rating > 7).
Permissions
For each action that be applied to any tag or namespace within Fluidinfo, there is:
- A policy (either 'open' or 'closed'); and
- A (possibly empty) list of exceptions to the policy.
The various actions that can be performed on a tag are read, update, create and see. The combination of the various actions with policies and exceptions provides a fine-grained permission model within Fluidinfo. It should be re-emphasized that only tags and namespaces have permissions allowing for various levels of control. Objects (the basic Fluidinfo data structure) do not have owners and so cannot be controlled by users/applications.
Examples of the permission model in various states are shown in the table below:[10]
| Tag or namespace | Action | Policy | Exceptions |
|---|---|---|---|
| tim/seen | read | closed | tim, meg |
| mike/opinion | update | open | |
| mike/ | create | closed | |
| meg/rating | see | open | |
| meg/rating | read | closed | meg |
Remove ads
The company Fluidinfo was founded in the UK in 2007 and operates out of New York City and Barcelona.[11] Esther Dyson provided an early-stage angel investment in the company.[12] Tim O'Reilly is also an investor in the company.[13]
Fluidinfo launched in alpha as "FluidDB" on August 17, 2009.[14] Developers can sign-up for access to Fluidinfo via their homepage. This is similar to the types of RESTful API access provided by other cloud services.[15][16][17] The company changed the name of the product from "FluidDB" to "Fluidinfo"[18] and won Top Technology Prize at the 2011 LAUNCH Conference.[19] During SXSW 2011, Tim O'Reilly named Fluidinfo as his favorite startup.[20]
Remove ads
- Freebase
- databaseLiquid/DBLiquid
- NoSQL
- DBpedia
- LinkedData
- Semantic Web
Wikiwand in your browser!
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
Remove ads