Freebase: Discussion about drakecaiman

Local Food: NRDC data?

2010-01-05T19:01:56.0000Z

Does the base include NRDC Eat Local data? For example, like: http://www.nrdc.org/health/foodmiles/results.asp?state=1&season=7

If not I'm going to try and t get it loaded.

Airline: Airline designator properties/types

2010-01-05T18:46:30.0013Z

IATA's non-uniqueness is the bad kind. The codes can be used by multiple carriers in two ways: First, by old codes being reused (if an airline goes out of business, say), which we could probably handle by deciding only to deal with current data; but, Second, IATA also uses something it calls "controlled duplicates", which means that airlines which operate in different regions can have the same codes (e.g., ATA and Air-taxi Europe both have the code TZ).

Organism Classification Rank: Higher/lower rank

2010-01-05T18:28:49.0013Z

I think I confused myself here. There is /biology/organism_classification/higher_classification and there is /biology/organism_classification_rank/higher_rank. I think the complaint is that /biology/organism_classification_rank/higher_rank is not filled out enough for the population of real world /biology/organism_classification/higher_classification data

Island: Max properties unique

2010-01-05T18:17:06.0023Z

Good catch. Added to the current uniquification bug.

Organism Classification Rank: Higher/lower rank

2010-01-05T18:14:46.0014Z

Agree completely. In fact, see the data at the top of this app which is what I've been using to validate what we've currently got in the tree :-)

Organism Classification Rank: Higher/lower rank

2010-01-05T18:10:37.0013Z

I agree, which is why I proposed what I said above. Because we are using Organism Classification to model Organisms as well as Ranks its likely to be less specific for Ranks than an individual organism. Im fine with adding Family in there but I think Tribe and Subtribe need to be there also.

Organism Classification Rank: Higher/lower rank

2010-01-05T18:06:05.0032Z

While it's true that subtribe is the next highest possible rank above genus, there's no requirement that any organism is actually assigned a subtribe; the only required classifications are the 8 major taxonomic ranks (division, kingdom, phylum, class, order, family, genus, species); all the minor ranks (tribe, suborder, superfamily, etc) are optional. It's perfectly valid (and in fact very common) for a genus to be connected directly to a family rather than having a tribe (and possibly subtribe) inbetween; see for example Gorilla gorilla.

Developer Support: timebased news

2010-01-05T17:37:53.0042Z

Hello: I want to know how to retrieve time based news from freebase can you please let me know how to retrieve it . Thanks Venkat

Organism Classification Rank: Higher/lower rank

2010-01-05T17:32:21.0018Z

I had intended it for the most immediate higher and lower rank of a classification.

ITIS has Subtribe as the next highest rank above Genus. Wikipedia is more nuanced, since it could be Tribe, Subtribe or Alliance.

I would be fine with (for these higher taxa) de-normalizing it and having Family, Sub-Tribe and Tribe all connected.

If you want me to run some stats on the data we have already to determine when we have in fact connected a Genus to a Family rather than a Tribe I can do that....

Organism Classification Rank: Higher/lower rank

2010-01-05T17:07:10.0004Z

Right, so it looks like we're all confused as to what it's for :-)

Unless anyone speaks up, I'm going to continue with the assumption that we all made that it's for the possible higher/lower ranks and fill that data in sometime in the next few days (unless I forget).

Airline: Airline designator properties/types

2010-01-05T16:53:47.0008Z

Sounds good to me. The only thing I'm not sure about (I haven't looked very hard though) is whether the IATA designator is non-unique in that an airline can have more than one or non-unique in that one code is used by more than one airline, as its only the latter which would prevent us using an enumeration.

please delete this topic

2010-01-05T16:00:52.0017Z

I added it before I realized that there is already the Johann Gottfried Bernhard Bach topic.

Island: Max properties unique

2010-01-05T07:27:38.0018Z

Is there a reason why max length and max width properties of /geography/island are not unique? I think they should be made unique.

Building complex: Include Project Focus

2010-01-05T07:17:03.0000Z

I think Project Focus should be an included type of Building complex.

milagrosbara: Broa & Manuel Quiroga Losada

2010-01-05T00:40:32.0000Z

Hi milagrosbara, welcome to Freebase!

I noticed you added record labels to Manuel Quiroga Losada's topic. Excellent. Unfortunately, however, you selected a type of bread as one of his record labels (broa). Bread cannot also be a record label :) If there was or is a record label named Broa, please create a new topic for it. If you need help doing that, just ask!

Thanks, and again welcome to the community

Australian Suburb: SSC

2010-01-04T22:22:08.0016Z

I'll create a task to set up the property and namespace for state suburb codes, so that we can enter these as foreign keys.

Airline: Airline designator properties/types

2010-01-04T21:56:13.0000Z

This is a relic, basically -- these predate any standardized notion of keys, and we tried out a lot of different ways of handling them. These should probably just be gardened into enumerated keys or machine-readable strings; types are definitely not the best way to handle this. A brief look suggests that the IATA two-digit designator is non-unique, so might be better off as a string. But the ICAO is apparently unique, so that would be a good candidate for a key. We already have an ICAO namespace, so we just need to create the appropriate sub-namespace (/authority/icao/airline_designator?) and then refactor the data a bit.

Does this sound like a reasonable plan?

Organism Classification Rank: Higher/lower rank

2010-01-04T20:51:53.0000Z

Yeah, it's sort of odd -- looking at the data, I was expecting that the values should be all the ranks which can possibly be the next higher or lower rank, but it seems like most of the data is just for the sub/super/infra/etc. ranks, which I don't think really fits that description.

Column: Unsyndicated columns?

2010-01-04T18:42:07.0006Z

Great! Now all we need is to figure out how to model both syndicated and unsyndicated columns (harking back to the first two posts in this thread), and we can get this schema promoted.

Organism Classification Rank: Higher/lower rank

2010-01-04T12:44:08.0013Z

That's exactly what I'm trying to use it for, but in that case it's missing some really obvious data: for example, genus doesn't have a higher rank of family, so I startted wondering if there was something I was missing :-)

Organism Classification Rank: Higher/lower rank

2010-01-04T12:37:35.0006Z

Sanity checking on the higher/lower classifications in Organism Classification?? (I'm guessing.)

Organism Classification Rank: Higher/lower rank

2010-01-04T12:20:02.0019Z

What are the higher/lower rank properties on the Organism Classification Rank type intended for?

Australian Suburb: SSC

2010-01-04T04:21:14.0013Z

Australian Suburbs can have a "State Suburb Code" according to the ABS.

http://www.abs.gov.au/AUSSTATS/abs@.nsf/mf/2033.0.55.001

This would let us reconcile statistics (population, etc) easily.

Airline: Airline designator properties/types

2010-01-02T12:27:28.0013Z

I'm strugggling to understand the value of the IATA/ICAO designator properties on /aviation/airline and the associated types. What does this property/type combination give us that an enumerated property wouldn't?

Column: Unsyndicated columns?

2009-12-31T20:21:28.0006Z

This looks good. Example: This View of Life

Column: Unsyndicated columns?

2009-12-28T17:34:37.0000Z

Type created: Collection of columns. Comments requested!

Column: Unsyndicated columns?

2009-12-28T16:56:37.0005Z

Done.

Column: Unsyndicated columns?

2009-12-28T16:24:34.0005Z

Krsalis: If you make me an admin of the columns base, I can create the "Collection of Columns" type and properties.

Column: Unsyndicated columns?

2009-12-22T23:21:32.0000Z

Ahhh, OK. +1 on the new type.

Column: Unsyndicated columns?

2009-12-22T02:31:23.0000Z

Wait. Back up. The whole "collection of columns" idea was in response to your first reply to this thread, wherein you resisted the notion of creating topics for each individual column, and instead just "start with the column topic, give it a year range, and link that CVT to the collection", as you put it. My thought was that we could use one model for that approach, which would allow people to connect columns to collections without needing to go ahead and create topics for each individual instance of the column; we could still use the existing publication model alongside that to enable people who want to link individual columns. Yes? Or did I completely misunderstand your previous post?

Column: Unsyndicated columns?

2009-12-22T01:02:26.0009Z

Publication can be used to model a collection of columns where each column article is a published work. For columns that don't have individual titles, I'm guessing the topic name would follow TV talk show episodic name format -- like "January 10, 1996". After all, usually it's not the column in its entirety that's collected, but individual pieces, sometimes within a date range, sometimes grouped by subject matter.

Can you elaborate on how exactly "collection of columns" would link the collection to its content? It's not clear to me what the alternative would be.