spatialed

Roadmap of future features: What links here

2008-07-24T19:58:20.0012Z

I like this idea alot... let's give it some thought.

Roadmap of future features: Clone one type from another

2008-07-24T19:45:52.0012Z

So, at long last, I think we've got the feature y'all were looking for. See my blog post on delegated properties.

Location: Contains/Contained By

2008-07-23T15:44:01.0000Z

Can you put a limit on this? I always see more than one level on these items and its frustrating. Can you guys just cap that field at 1?

Roadmap of future features: What links here

2008-07-21T16:42:06.0012Z

Since it's not always appropriate to include all the suggested incoming properties in a schema, would it be possible to have a "What links here" page that shows the topics that link to this topic in one of their properties? It'd be useful for when you see an empty topic and wonder why it exists.

Roadmap of future features: Option to require included type

2008-07-18T23:48:42.0013Z

Beyond the ranking suggestion above, people have tried to add bands and tv shows to the influence domain, and I'm not really watching the additions that carefully.

Is there a way to require an included type (person, in this case)? Tv shows and bands aren't the focus for the domain, but beyond saying that in the description, it's hard to monitor.

Help Center: Queries Confusing Me...

2008-07-15T01:45:27.0000Z

Actually, you can get the queries for most things! Take a look at this page: http://tinyurl.com/6h28kt -- that's a list of computer games where I've added the "platform" column then filtered on "Xbox 360".

Then click on "Use Results" and then "See the query".

That gives you a MQL query you can use in your own apps or wherever.

Creating and Publishing Personal Domains: Limiting Topic Editing Rights

2008-07-12T00:05:39.0005Z

Agreed. We hope to have our internal bug (and feature) tracking system visible and editable externally in the next month or two which should provide more visibility. With respect to this particular feature, it hasn't really gotten past the discussion stage here -- we're more focused on the basic open data contribution cases at this stage.

Help Center: See my history?

2008-07-11T23:36:52.0012Z

http://dev.mqlx.com/~nick/reports/userdetail.html?user=/user/evening

Try it without the escaped "/" as "%2F"

(Its possible this might be a site only accessible internally at Freebase Headquarters?)

Here's a very useful page of tools:

http://www.freebase.com/view/guid/9202a8c04000641f8000000005bbe084

Help Center: See my history?

2008-07-11T23:18:04.0000Z

It looks like the client team has already fixed this in our upcoming release - thanks for reporting this, though.

Help Center: See my history?

2008-07-11T19:15:28.0012Z

oops, that didn't paste quite right. let me try again.

warning

mjt.json_from_js: undefined value is illegal in JSON

error

error
evaluating codeblock #top
{"lineNumber":null,"name":"SyntaxError","message":"Expected identifier, string or number","prev_lines":[],"the_line":[[[ERROR: undefined value]]],"next_lines":[]}
SyntaxError: Expected identifier, string or number

---NaN-->

Help Center: See my history?

2008-07-11T19:14:19.0000Z

This is a different one. When I go to the link you provided above (http://dev.mqlx.com/~nick/reports/userdetail.html?user=%2Fuser%2Fevening), I get a warning and error. I've copied it below.

warning
mjt.json_from_js: undefined value is illegal in JSONerror
errorevaluating codeblock #top{"lineNumber":null,"name":"SyntaxError","message":"Expected identifier, string or number","prev_lines":[],"the_line":[[[ERROR: undefined value]]],"next_lines":[]}
SyntaxError: Expected identifier, string or number

---NaN-->

Help Center: See my history?

2008-07-11T02:21:49.0012Z

Is this a different error than the one you reported earlier? If so, could you provide more details?

Help Center: See my history?

2008-07-10T17:41:47.0012Z

FYI, looks like there is an error on the userdetail report

Help Center: See my history?

2008-07-10T17:40:38.0005Z

Thanks!

Creating and Publishing Personal Domains: Limiting Topic Editing Rights

2008-07-10T03:47:04.0000Z

Just scheming, so to speak.

In general, transparency about the feature road map is a good thing, although I can understand the need to protect trade secrets.

Creating and Publishing Personal Domains: Limiting Topic Editing Rights

2008-07-09T21:55:12.0000Z

We've certainly discussed that capability - and use it special cases in the application, but making this a generalized permission feature is probably a ways out. What are you trying to do?

Roadmap of future features: Rank of autosuggested topics

2008-07-09T19:37:25.0012Z

It would be helpful if the rank of autosuggested topics took into consideration the included types of the expected type. Here's an example:

If I am adding an influence, the autosuggest list should prioritize people over other types (films, magazines, etc), because people is an included type of the expected type (influence).

Creating and Publishing Personal Domains: Limiting Topic Editing Rights

2008-07-09T00:51:07.0012Z

Are there any plans to allow for administrators to specify which users can edit a given topic?

Help Center: See my history?

2008-07-08T20:36:13.0001Z

I've been told that this has been fixed in the upcoming release.

Help Center: See my history?

2008-07-08T19:27:50.0044Z

Hmmm, seems like you may have stumbled on to a regression. I'll file an internal bug, but in the meantime, you can try this URL: http://dev.mqlx.com/~nick/reports/userdetail.html?user=%2Fuser%2Fevening

Thanks for reporting this!

Data Modeling Guide: How can I set "linked in as" for types that I generate

2008-07-08T18:58:07.0028Z

It should be nigh-instantaneous. If you don't see one you expect to see, try refreshing the cache (the F8 key will add a little menu to the bottom of the page -- click the "refresh page" link, then refresh your browser). There is also a bug with suggested properties sometimes not showing up which I believe will be fixed in the next release.

Roadmap of future features: Spreadsheet of "Top Ten" lists

2008-07-08T16:01:16.0005Z

Some years ago, I compiled an interesting "Top Ten List" gallery in a spreadsheet, now found here:

http://www.mywikibiz.com/Image:Top_Ten_Lists.xls

Do you think there would be some useful and/or entertaining rendering of this spreadsheet in Freebase?

I am clueless in terms of developer code, so don't even think of trying to walk me through something complicated. What I'm basically saying is that I release the content of this database of ninety-eight (98) Top Ten lists for re-issue by Freebase, if someone cares to figure out how to render it in a useful or entertaining way.

Kindly,

Greg

Help Center: See my history?

2008-07-08T15:27:40.0005Z

Is there a way to see my entire activty history? I added some stuff yesterday with the plan to go back and fill in data, but now I'm not sure if I remembered all that I added :) And the history in my user account doesn't go back far enough (not even the expanded view).

Is there a way to see this kind of info?

Data Modeling Guide: How can I set "linked in as" for types that I generate

2008-07-08T02:42:31.0012Z

That's actually a good way of explaining reciprocal properties.

Do you know how much lag time to expect from the time a property is put up, to when the suggested property appears on the other type?

spatialed: Properties co-typed as other types

2008-07-01T15:34:09.0005Z

Thanks, Ed.
I think Physiognomy and Satellite sensor status (the properties) should be separate, discrete objects than Physiognomy and Satellite sensor status (the topic and LC) and not conflated. You do have a separate Physiognomy type (http://www.freebase.com/tools/schema/user/spatialed/land_cover/physiognomy) - should that have included types of topic and LC?

spatialed: Properties co-typed as other types

2008-07-01T04:09:05.0012Z

Sure but they were purposeful typings. LC is a bucket type I created for all types that have something to do with land cover mapping even if they are best placed in another domain. They are usually topics too. No problem if you want to detype them. I've put that project on the shelf for a little bit and know how to pick it back up later.

spatialed: Properties co-typed as other types

2008-06-30T16:41:39.0012Z

Hi Ed,

I've noticed that you have 2 properties, Physiognomy and Satellite sensor status cotyped as LC and Topic. I'm guessing this might have been an errant mistyping due to autocomplete. I'd like to detype them - is that ok?

Location: Contains/Contained By

2008-06-20T19:33:14.0000Z

One level is sufficient, Tyler. One of our planned features is transitive property comprehension (like containment and organism classification hierarchy), so there is no need to denormalize the hierarchy completely.

Location: Contains/Contained By

2008-06-20T18:48:46.0005Z

How deep should I go? For instance, I'm working on the Empire State Building. Generally, it is contained by New York. If one clicks to see New York, they'll see that the city is contained the state, and the state by the country, then continent, then earth.

In this sense, should I list that the Emprie State Building is contained by: New York, New York, United States, North American, and Earth?

I haven't been doing this because I think its cleaner to just list the most immediate contained by and followed the path if needed. I guess I'm asking is my way correct or not?

Thanks!

Data Modeling Guide: How can I set "linked in as" for types that I generate

2008-05-09T17:56:06.0007Z

There may be something I am missing: it looks like you’ve answered your own question! (“If you want to change that name, and you have the necessary permissions, you can change it on that other type.”) I’ll try to break it down, though.

When looking at the schema for a type, you can only edit the properties on that type. The “linked in as” is the name of the reciprocal property on some other type, so you can’t edit that directly; you must visit the other type to change it.

To create a “linked in as,” a reciprocal property, is very simple. Once you have a property from one type to another, go visit the schema for that other type. At the bottom of the schema editor, you will see “Suggested Properties”; these are un-reciprocated incoming properties from other types. If you edit the name of one of those, you have not only picked up a new property with its “linked in as” already set, you have now changed the “linked in as” on the other type.

Please note that the schema editor is being redesigned, so the details of this process (though not the fundamental concepts) may change.

Now, if you don’t have the rights to edit the other type, you’re out of luck. Let’s say you make a private type called Hater with a property called “People Hated” that expects Person. Unless you’re an administrator of the People domain, you can’t reciprocate that property as “Hated By.” And that’s just as well; we don’t want everyone on the system to be able to edit all the types, which is why we have the administrator system in place. If you think that known by whom a person is hated is critical information to the Freebase community, you can ask the People administrators to reciprocate the property, or even to promote your Hater type into their domain.

Does that help?

Data Modeling Guide: How can I set "linked in as" for types that I generate

2008-05-09T05:42:58.0005Z

Cannot see how I can set "linked in as" for types that I generate. Is there something that I am missing?

I'm reading this a bit differently - the (links in as...) label appears in Type Editor for any properties that link from another type. For instance, on the type 'film' there is a property called 'Directed by' which has an expected type 'Director' which links in as 'Films directed'. 'Films directed' is the display name of the property on the other type - so if you want to change that name, and you have the necessary permissions, you can change it on that other type.

Thanks for your reply

spatialed: Cyclical included types

2008-04-17T03:03:35.0000Z

Good catch. Thanks. I was still figuring out how to work with Included types when I created those schema. They probably still need some work but I removed the cyclical relationships. Let me know if you see any other problems. I plan to get back to these schema and start adding a lot more data for them May-June.

spatialed: Cyclical included types

2008-04-16T20:00:49.0007Z

you have a cyclical relationship:

http://freebase.com/view/schema/user/spatialed/default_domain/satellite_image_product

i click on the first included type "Land cover classification system" of "Satellite Image Product"

http://freebase.com/view/schema/user/spatialed/default_domain/land_cover_classification_system

and "Land cover classification system" has as its first included type "Satellite Image Product"

spatialed: Cyclical included types

2008-04-16T18:30:13.0000Z

i'm seeing a cyclical relationship in:

http://freebase.com/view/schema/user/spatialed/default_domain/satellite_image_product

a satellite image product has itself as an included type.

is this an error?

spatialed: Deprecated /book types

2008-03-19T01:24:47.0000Z

Thanks Bryan for the heads up and nudge that it affected me. I used reviewer only because it seemed to fit best but I didn't really like it. I think I'll switch to Author but the way that type is described it may not be appropriate either...

spatialed: Deprecated /book types

2008-03-18T22:57:10.0005Z

Hi Ed,

I know you subscribe to the data-model list, but I wanted to let you know that I noticed that your type /motorcycle/motorcycle_product_review has a property that expects one of the types listed in the email. You can review the email here.

spatialed: Units of moment of force

2008-02-18T21:37:45.0007Z

You should be able to add inch-pounds. Add a new instance of Unit of Moment of Force and give it a name. You must also give it a “Dimension” (Torque) and a “Canonical Abbreviation” (in-lb?) in order to be able to use it with a property definition. An equivalence in Newton-meters is also encouraged (0.112984829, I believe).

spatialed: Units of moment of force

2008-02-17T04:44:21.0000Z

Oops. I meant to add inch-pounds and went with an existing topic I mistakenly thought was synonomous. Similarly, I mistakenly thought that kilograms per cubic meter was a metric equivalent. Inch-pounds does need to be included though.

Help Center: Queries Confusing Me...

2008-02-16T18:41:31.0007Z

I agree with the last statement. I was wondering exactly the same thing.

"Why not show, on the site, the query used to generate the data on the page?"

spatialed: Units of moment of force

2008-02-16T02:18:53.0007Z

Torque is usually measured in force × distance: foot-pounds, Newton-meters (the SI unit). This can be decomposed to mass × area ÷ time-squared; I have never heard of torque measured in units of density (mass ÷ volume, kg/m³) or pressure (force ÷ area, psi). Where are you seeing torque measured in these units? It may be a field-specific jargonistic
use of the term, but it’s not one I’ve heard before.

spatialed: Units of moment of force

2008-02-16T00:35:01.0007Z

Ok. Why are they odd? I added them because torque is commonly measured in terms of pounds per square inch or kilograms per cubic meter. How should I enter torque data?

spatialed: Units of moment of force

2008-02-13T22:18:34.0005Z

Ed, there were a couple of odd topics that were typed by you as units of moment of force (kilograms per cubic meter and pounds per square inch). I have de-typed them, but you may want to check if you had any properties using them as units. Please double-check them.

spatialed: Cyclical included types

2008-01-14T23:30:56.0000Z

Where do you see land cover as an included type of classification system? I don't see land cover (or any other types) as an included type of classification system. However, classification system is an included type of land cover. The name is actually "Land cover classification system" to identify it as a subset of "Classification system". I've changed the type key to reflect this nestedness. The new address is /user/spatialed/default_domain/land_cover_classification_system

If there is a cyclic relationship somewhere let me know and I will change it because it would be an error.

spatialed: Cyclical included types

2008-01-12T00:53:11.0018Z

the type /user/spatialed/default_domain/land_cover has as an included type /user/spatialed/default_domain/classification_system.

but /user/spatialed/default_domain/classification_system has /user/spatialed/default_domain/land_cover as an included type too,

creating a cyclic included types relationship. is this an error?

spatialed: Cyclical included types

2008-01-12T00:53:11.0005Z

the type /user/spatialed/default_domain/land_cover has as an included type /user/spatialed/default_domain/classification_system.

but /user/spatialed/default_domain/classification_system has /user/spatialed/default_domain/land_cover as an included type too,

creating a cyclic included types relationship. is this an error?

Help Center: Queries Confusing Me...

2007-12-31T12:38:33.0000Z

Thanks for the reply. I do have a suggestion/question though for the site in general. Why not show, on the site, the query used to generate the data on the page?

For example, this page: http://www.freebase.com/view/reorder/topic/en/xbox_360?propertyId=%2Fcvg%2Fcvg_platform%2Fgames_on_this_platform&returnUrl=http%3A%2F%2Fwww.freebase.com%2Fview%2Fxbox_360

It would be good to see the query used to generate all of those results and would make it easier for people to get to grips with it.

Roadmap of future features: Clone one type from another

2007-12-10T22:04:07.0007Z

Thanks if this was to me (Ed not Brian). I plan to delve into MQL soon. I'm trying to get a decent handle on data modeling first. Also, programming skill is not one of my strongest attributes.

Roadmap of future features: Clone one type from another

2007-12-10T20:30:46.0007Z

Brian, have you looked at using MQL (Metaweb Query Language) directly for some of the more advanced operations, such as mass creation of topics with very similar values, duplicating a type with minor changes, or querying for all topics meeting certain criteria? It's a more powerful way for developers to use Freebase data without going through the UI.

If you're interested, the API is a good place to start. Try things in the query editor on sandbox to see how they work.

Roadmap of future features: Clone one type from another

2007-12-10T18:53:22.0007Z

Depends on what you mean. If you are referring to the process of making an extended type, then it would be most important to exclude specific properties from the existing type with a single step. If the extended type is then treated as a regular type afterwards, the user could always add new types specific to it.

Roadmap of future features: Clone one type from another

2007-12-10T18:38:44.0007Z

Actually, we're working more actively on this kind of feature than the one I previously described - something we're calling 'extended types', which would allow you to select an existing type to use all its properties but be able to add new properties to it - but this is probably at least a few weeks off at this point.

What do you think is most important? Adding, removing or relabeling properties from an extended type?