Freebase: Discussion about jdouglas

Rivalry: Rename to Celebrity Rivalry

2009-11-12T08:34:08.0031Z

The purpose should be clear to any developer as the full key is /celebrities/rivalry

It's just that it might get confusing to someone entering data from the client or autocomplete, and a name change would resolve that.

Mythology: Location in Mythology

2009-11-12T08:31:10.0024Z

ed,

Thanks very much.

I did forget the most important property though, mythology! Otherwise there is no way to link Valhalla to Norse mythology.

Rivalry: Rename to Celebrity Rivalry

2009-11-12T08:30:15.0042Z

So long as its just the name that's changed rather than the key, that shouldn't cause any queries to break. I say go for it!

Battery: Schema comments

2009-11-12T08:29:42.0013Z

I've removed the included types. I'd argue that manufactured component category shouldn't be used for branded things - the category is electric car battery instead of Toyota Prius battery, or Vacuum cleaner instead of Hoover or Dyson. I'm considering having a new "manufactured component line" type for branded things like Toyota Prius Battery.

Common Dimension: Voltage

2009-11-12T08:23:37.0027Z

Thanks Chris

Business Location: Classification property for Retail Location?

2009-11-12T08:15:53.0014Z

That would work, although I'd try to avoid using the word 'type' in schema - it gets confusing when discussing schema types.

Architecture: Structural height

2009-11-12T08:10:07.0008Z

I assume occupied height is measured to the floor level of the occupied space? (and not to the ceiling/roof above it)

If to the floor level, for any building with an inaccessible roof (i.e. no roof top terrace, and ignoring access for maintenance and cleaning), the occupied height of a building will be different from the building height (measure to the top of the superstructure , excluding antennae and spires). As most tall buildings have an unoccupied plant room on the topmost level, the difference can be significant.

In theory occupied height belongs on building, although in practice it's probably only recorded for skyscrapers.

Literary Series: Genre?

2009-11-12T05:00:48.0016Z

Oh rock on. Thanks for the perspective. Lightweight containers make pedantic librarians nervous. ;)

General Support: First Super Star of Indian Cinema

2009-11-12T04:16:57.0049Z

1) Raj Kapoor 2) Dilip Kumar 3) Dev Anand 3) Sunil Dutt 4) Shammi Kapoor 5) Raaj Kumar 6) Sanjeev Kumar 8) Dharmendra 10) Jetendra 11) Amitabh Bachchan 12) Shah Rukh Khan 13) Rajendra Kumar 14) Manoj Kumar 13) Rajesh Khanna

Rivalry: Rename to Celebrity Rivalry

2009-11-12T01:47:10.0011Z

This sounds like a good suggestion to me. Does anyone else see a reason why this shouldn't be renamed? Are there any applications that use this type? Acre code search doesn't show any matches.

Film: Production credit, Executive versus the rest

2009-11-12T01:32:49.0025Z

I'd prefer the former, both pointing to film producer which would have films produced and films executive produced as a return linkages... Well that doesn't scan too well. Served as executive film producer on ... ?

Book Edition: Hide old ISBN?

2009-11-11T23:22:43.0014Z

Yes, thanks for reminding us!

Mythology: Location in Mythology

2009-11-11T23:15:04.0020Z

Done and done!

Business Location: Classification property for Retail Location?

2009-11-11T22:08:52.0005Z

How about "type of business location" as a name?

Business Location: Classification property for Retail Location?

2009-11-11T21:53:31.0001Z

Just came across this. I'd definitely support a business category property on business location.

It would be useful to model whether a business location operated by a company is a cafe or their offices.

Film: Production credit, Executive versus the rest

2009-11-11T21:52:01.0000Z

Well, that's pretty true. Thinking about it further, it does seem that an executive producer in film is a completely different sort of role than the other various types of producers (despite the similiarity of names), so creating a new property makes sense. Next question: should it expect the existing Film Producer type or a new Film Executive Producer type?

Mythology: Location in Mythology

2009-11-11T21:34:28.0029Z

Taking cue from the location type, I'd suggest the following:

Contains & Contained by both expecting "Location in Mythology". Asgard contains Valhalla in Norse mythology.
Also Adjoins expecting an "Location in mythology adjoining relationship".

In this manner we can build up relational maps of mythological worlds!

Mythology: Location in Mythology

2009-11-11T21:25:18.0032Z

That sounds fine to me. However, can you suggest another property or two that would help justify the broadened scope of the type's name? It currently only has the "Events at this location" property.

Mythology: Location in Mythology

2009-11-11T19:55:54.0014Z

d'oh. Just found Mythical event location.

Could we change the name of Mythical event location to Location in Mythology? Not all locations in mythology have events associated with them.

Thanks

Mythology: Location in Mythology

2009-11-11T19:50:31.0039Z

Could we have a "location in mythology" type?

I'd like to type Asgard and Valhalla as such.

Thanks

Architecture: Structural height

2009-11-11T17:26:30.0052Z

There is "Structural Height" on structure and "Height with Antenna" on skyscraper. There is note on the former saying "For Skyscrapers this should not include antennae or spires." So I guess I'm implying that the former means occupied height. Maybe it would make more sense to have it be the other way around, but I think the bottom line is: people only care about this distinction with skyscrapers and I've given them the slots to describe it so good enough? I could add occupied height to skyscraper, but then what should they put in for "Structural Height" ?

Rivalry: Rename to Celebrity Rivalry

2009-11-11T15:56:00.0070Z

This may get confused with other rivalries, such as football or college rivalries. I'd like to change the name to be clear in its purpose. (and some documentation wouldn't go amiss!)

Book Edition: Hide old ISBN?

2009-11-11T10:38:51.0000Z

Should the old ISBN property now be hidden?

Architecture: Structural height

2009-11-10T23:39:06.0038Z

A missing property that seems of interest amongst the height-loving skyscraper-o-philes is Occupied floor height.

Highest possible terrestrial-structure-based human viewing spot is the Occupied floor height.

Could be placed within /Structure or /Skyscraper (former makes the most sense as it already has the related roof height).

Film: Production credit, Executive versus the rest

2009-11-10T21:47:57.0038Z

I think the break would be pretty catastrophic given how many apps are built on Film now.

I would strongly prefer a new property over mediating the Producer relationship.

Battery: Schema comments

2009-11-10T21:43:00.0059Z

This is a tricky one, since Battery has its foot in two levels of the schema. Saying strictly that Battery is for the category would be esthetically pleasing, but would require the fairly silly state of having two "Toyota Prius Battery" topics -- one for the category and one for the manufactured component. I think the thing to do is not include either Manufactured Component or Manufactured Component Category, and just add them manually as necessary.
Sounds good.

Battery: Schema comments

2009-11-10T21:30:31.0006Z

I think they should. I''ve fixed this.
It depends. Battery has specific batteries, e.g. Toyota Prius Battery (a Manufactured Component); but it also works for more generic types of battery, e.g. Alkaline AA battery. (Manufactured Component Category). Should we assume that categories will be more prevalent than specific batteries?
Invention projects was what I was angling at, but on reflection it's unlikely that we'll have that much data on projects focusing on batteries (unlike construction projects for buildings) - so perhaps better if removed. If there is a project it can always be added manually.

Film: Production credit, Executive versus the rest

2009-11-10T21:16:47.0058Z

I prefer inserting the mediator, although it's a breaky change. It would bring film into line with TV shows, though: TV Producer term

Film: Production credit, Executive versus the rest

2009-11-10T20:57:33.0026Z

I believe it may be advantageous to separate out the role of an Executive Producer from that of the Producer (and Assistant/Associated Producer).

We could do it simply with a new property for Executive produced by, example on sandbox, that points to Film producer. Regular production and associated/assistant production would remain with original property.

(Better might be inserting a mediator between Produced by and Film Producer, with enumerated topics for Executive, Associate, Assistant, and blank for the regular credit.)

Any objections? Improvements?

Battery: Schema comments

2009-11-10T20:45:53.0037Z

Should the IEC and ANSI/NEDA properties be unique? I don't know anything about them, but this sort of data is often unique.
Instead of including Manufactured Component (which is for specific products), should Battery include Manufactured Component Category instead?
Does project focus make sense as an included type for Battery? I suppose it could, since each kind of battery must have been invented somehow.

Common Dimension: Voltage

2009-11-10T14:39:17.0011Z

Sorry; I did not read carefully. Instances of common dimension can only be added through MQL queries by domain administrators. Potential difference is now added (though the query timed out the first time!).

Common Dimension: Voltage

2009-11-10T05:52:17.0013Z

Yes, but it's not a Common dimension and not available in the drop down list in the schema editor of the client.

Common Dimension: Voltage

2009-11-09T19:20:04.0026Z

I think you may have overlooked potential difference. I found that by looking up volt, and seeing what dimension it measured.

Common Dimension: Voltage

2009-11-08T14:32:43.0000Z

I'd like to add Electrical Potential Difference (aka Voltage) as a Common Dimension (unless it's there already, and I'm missing the obvious). I've been trying to model batteries, and it would be a useful dimension to have.