Talk:Fluidinfo

message: 未翻譯內容如下：--Flame 歡迎泡茶 2012年11月16日 (五) 00:57 (UTC)
thread_title:  未翻譯內容 

message: 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".Robert Scoble video interview with Terry Jones. Retrieved on 2009-09-18. 
Fluidinfo emphasizes three aspects that make it unique among existing public data stores:
* Data model
* Query language
* Permissions
=== 數據模型 ===
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.Fluidinfo information overview Anyone can attach tags to any data object, but only people with the right roles can see and search these tags."FluidDB review", Peter Wayner. TechWorld.com. Retrieved on 2010-11-04.
===查詢語言 ===
The query language was designed to perform complex queries in as simple a manner as possible.Fluidinfo query language description 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 belowFluidinfo query language documentation:
* 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/keywords might be on an object with a value of [ "cool", "kids", "adventure" ]. The contains operator can be used to select objects with a matching value. The query mary/product-reviews/keywords contains "kids" would match the object in this example.
* Exclusion: You can exclude objects with the except keyword. For example has nytimes.com/appeared except has james/seen. The except operator performs a set difference.
* Logic: Query components can be combined with and and or. 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).
=== 權限 ===
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 belowSlideshare FluidDB presentation, pp. 68-69:
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
thread_title: 概述

message: 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.Fluidinfo information overview Anyone can attach tags to any data object, but only people with the right roles can see and search these tags."FluidDB review", Peter Wayner. TechWorld.com. Retrieved on 2010-11-04.
thread_title:  數據模型 

message: The query language was designed to perform complex queries in as simple a manner as possible.Fluidinfo query language description 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 belowFluidinfo query language documentation:
* 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/keywords might be on an object with a value of [ "cool", "kids", "adventure" ]. The contains operator can be used to select objects with a matching value. The query mary/product-reviews/keywords contains "kids" would match the object in this example.
* Exclusion: You can exclude objects with the except keyword. For example has nytimes.com/appeared except has james/seen. The except operator performs a set difference.
* Logic: Query components can be combined with and and or. 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).
thread_title: 查詢語言 

message: 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 belowSlideshare FluidDB presentation, pp. 68-69:
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
thread_title:  權限 

message: The company Fluidinfo was founded in the UK in 2007 and operates out of NYC and Barcelona."20 Hot NYC Startups You Need To Watch", Nick Saint. Business Insider. Retrieved on 2010-11-07. Esther Dyson provided an early-stage angel investment in the company."Fluidinfo – a database aiming to socialize information", Marina Zaliznyak. TechCrunch Europe. Retrieved on 2010-11-07. Tim O'Reilly is also an investor in the company."Dancing out of time: Thoughts on asynchronous communication", Terry Jones. O'Reilly Media. Retrieved on 2010-11-08.
Fluidinfo launched in alpha as "FluidDB" on August 17, 2009.Fluidinfo blog 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.Rackspace Cloud API page. Retrieved on 2010-12-15Amazon Simple Storage Service (S3) REST API page. Retrieved on 2010-12-15  The company changed the name of the product from "FluidDB" to "Fluidinfo"Blog post. Retrieved on 2011-02-05. and won Top Technology Prize at the 2011 LAUNCH ConferenceLAUNCH 2011 Winner announcement. Retrieved on 2011-03-08.. During SXSW 2011, Tim O'Reilly named Fluidinfo as his favorite startupBusiness Insider. Retrieved on 2010-03-14.
thread_title: 現狀

message: * Freebase
* databaseLiquid/DBLiquid
* NoSQL
* DBpedia
* LinkedData
* Semantic Web
thread_title: 參見

message: 各位维基人：
我刚刚修改了Fluidinfo中的2个外部链接，请大家仔细检查我的编辑。如果您有疑问，或者需要让机器人忽略某个链接甚至整个页面，请访问这个简单的FAQ获取更多信息。我进行了以下修改：
*向 http://doc.fluidinfo.com/fluidDB/overview.html 中加入存档链接 https://archive.is/20120708095521/http://doc.fluidinfo.com/fluidDB/overview.html
*向 http://doc.fluidinfo.com/fluidDB 中加入存档链接 https://archive.is/20130123053526/http://doc.fluidinfo.com/fluidDB
有关机器人修正错误的详情请参阅FAQ。
祝编安。—InternetArchiveBot (報告軟件缺陷) 2017年7月31日 (一) 15:23 (UTC)
thread_title:  外部链接已修改