Compound Value Type
From Freebase
| Line 2: | Line 2: | ||
A '''Compound Value Type''' is a [[Type]] within Freebase which is used to represent data where each entry consists of multiple fields. | A '''Compound Value Type''' is a [[Type]] within Freebase which is used to represent data where each entry consists of multiple fields. | ||
| + | Compound value types, or CVT's are used in freebase to represent complex data. It may be a little confusing at first, but CVT's are a very important part of the freebase schema, and one of the things that makes it unique, and able to represent so much. | ||
| + | Figure following example: | ||
| + | Population for a city is something that changes over time. That means, whenever you query freebase for population, you are at least implicitly asking for a population at a certain date. 2 Values are involved, a number of people, and the date. Here's a situation where a CVT becomes extremely useful. Without one, to model population data, you would need to make a topic, and name it something like 'vancouver's population in 1997', and submit the information over there. | ||
| + | |||
| + | A CVT can be thought of as a topic that does not require you can make a display name. CVT's, like normal topics, have a GUID that can be referenced independently. The freebase client however treats them much differently than topics. | ||
| + | In most cases, every property of the CVT should be a disambiguiation property. | ||
[[Category:Schema]] | [[Category:Schema]] | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
[[Category:Article stubs]] | [[Category:Article stubs]] | ||
Revision as of 20:55, 2 November 2009
Help us improve the Freebase wiki!
This article is a stub. You can help us by filling out more information. Just login with your Freebase credentials, and start editing!
A Compound Value Type is a Type within Freebase which is used to represent data where each entry consists of multiple fields. Compound value types, or CVT's are used in freebase to represent complex data. It may be a little confusing at first, but CVT's are a very important part of the freebase schema, and one of the things that makes it unique, and able to represent so much.
Figure following example: Population for a city is something that changes over time. That means, whenever you query freebase for population, you are at least implicitly asking for a population at a certain date. 2 Values are involved, a number of people, and the date. Here's a situation where a CVT becomes extremely useful. Without one, to model population data, you would need to make a topic, and name it something like 'vancouver's population in 1997', and submit the information over there.
A CVT can be thought of as a topic that does not require you can make a display name. CVT's, like normal topics, have a GUID that can be referenced independently. The freebase client however treats them much differently than topics. In most cases, every property of the CVT should be a disambiguiation property.
