Webpage

Webpage: How do I query these for a given guid?

2008-05-24T01:46:45.0007Z

I finally figured it out, I don't know why this was so hard, but it was:

[ { "guid" : "#9202a8c04000641f8000000000166606", "type" : "/common/topic", "webpage" : { "uri" : null } }

]

Webpage: How do I query these for a given guid?

2008-05-24T01:40:35.0012Z

I can't for the life of me figure out how to get weblinks using MQL. I've been using http://www.freebase.com/view/guid/9202a8c04000641f8000000000166606 as my example...

Webpage: How does webpage differ from weblink?

2008-05-01T17:46:42.0000Z

Thanks!

Webpage: How does webpage differ from weblink?

2008-05-01T17:37:45.0007Z

Basically, a specific property with an expected type of "webpage" is useful if you want a way to capture/retrieve webpages of a certain type, or with a specific semantic value. For example, the type Written Work has a webpage property for "online versions", which, if used properly, will allow on-line-reading users to quickly filter on all works that are available online.

The default "weblinks" property should hold everything else; in the case of "written work", it might be a link to a page about the work on the author's or publisher's website, or a link to a fan site.

Note that all links appear in the "weblinks" section. The "type" column allows you to select which property, if any, to assign the link to.

Webpage: How does webpage differ from weblink?

2008-05-01T03:00:05.0005Z

I noticed that some people use /webpage/ as a User Created Property in the same way that I've been using the "Weblinks" Included Property (listed in schema view as "Web Link(s)" with the Expected type of /webpage/). When should a model use /webpage/ as a secondary User Created Property instead of just using the primary Included Property?

Webpage: Unable to pull Webpage Type into my own Types

2007-10-17T06:32:32.0000Z

A web page isn't intended to be used in the same way that a web site is. Its the difference between an individual article on the New York Times site and www.thenewyorktimes.com itself.

Webpage: Unable to pull Webpage Type into my own Types

2007-10-13T04:57:59.0007Z

I would think there are a few of these "primitive" Types that users would want to reuse. Otherwise wouldn't we potentially end up with a large number of duplicate Types? Isn't that just as bad as duplicate Topics?

Webpage: Unable to pull Webpage Type into my own Types

2007-10-12T20:50:56.0007Z

Compound value types (of which webpage is one) are currently filtered out as options on included types - this is done because these types typically should not be named objects in the system -- but perhaps this requirement should be revisited.

Webpage: Unable to pull Webpage Type into my own Types

2007-10-11T23:48:45.0007Z

Compound value types do not appear in the autocomplete menu. I'm not sure whether this is by design or a bug, but I'll look into it.

Webpage: Unable to pull Webpage Type into my own Types

2007-10-11T05:17:55.0012Z

I've been unable to add the Webpage Type into my own Types. For example, I created, as an experiment, a Type called Wikipedia URL as a way of capturing the Wikipedia URL should a user replace the Wikipedia extract with their own text. So what I need for my Type are the two properties of the Webpage Type. But when I search for it through the Included types : Add new, it doesn't come up as one of the results. Yet if I search for Webpage in the general search engine (top right) it's the first hit as a Type and a Type Profile. I noticed someone else was having the same problem and mentioned it elsewhere.

Webpage: "title" property should just use "name" property instead

2007-08-27T23:25:01.0007Z

/internet/website seems kind of heavyweight. i'm looking for something that's much closer to a uri, but with a bit of indirection so that it can handle multiple uris that point to the same thing and also allow cotyping as a topic. /common/webpage is pretty close to being the right thing except that it's a CVT so it doesn't have the right sharing behavior. i'll play around with my own types a bit and see what i come up with...

Webpage: "title" property should just use "name" property instead

2007-08-27T17:54:56.0007Z

It seems like you want something that works more like Website --- no? The issue, I'd imagine, is that webpage is the standard property on topics, not website. The thought was that people are pretty likely to link to all kinds of miscellaneous web URLs from topics, most of which wouldn't merit a display name.

Webpage: "title" property should just use "name" property instead

2007-08-25T03:07:22.0007Z

ah, i hadn't realized that /common/webpage had become a cvt. i don't think that makes sense
according to the usual semantics of compound value types, though i see how it works
better by invoking the cvt code in the freebase.com client.

the thing is, i'm working on a bookmarking app, where webpages/uris can be first-class topics.
if something is to be a discussion hub it should have a display name. some uniqueness must
also be maintained - at most one "webpage object" should be created per uri. i was expecting
to use /common/webpage for this.

currently it doesn't seem like webpage works this way - it puts the display name in an unusual
place, and causes the creation of lots of redundant instances of /common/webpage.
there is a lot of unnecessary data duplication going on to have a separate /common/webpage
for every reference to every uri.

Webpage: "title" property should just use "name" property instead

2007-08-24T23:01:42.0007Z

Not sure what you mean when you say most webpage objects display badly. Where? Outside of Freebase.com?

Using the name property would cause a number of problems for our existing UI in Freebase -- namely it would require the user to input a name for the webpage before inputing the URL. The URL is what we consider the primary input here. We've added specialized code to populate the title with the URL if a user fails to input one.

Aside from simplifying input, we don't want people to confuse webpages with websites... a webpage is really like a weblink... whereas a website is a root domain in most cases. There are probably many interesting webpages (links) to link to on amazon.com or cafepress for instance, but we don't necessarily want people to title each of these and create a topic about them -- this is one of the points of the CVT/mediator structure.

Webpage: "title" property should just use "name" property instead

2007-08-24T22:58:33.0000Z

Some Web pages are badly-titled; it is useful to know both the title and what the page is. That said, the name should probably be what is entered in webpage-valued properties, rather than the title.

Webpage: "title" property should just use "name" property instead

2007-08-24T22:26:02.0005Z

right now, most webpage objects display badly by default because they don't have
name properties. instead they have a "title" property. i would propose to just use
"name" to hold the title, which both simplifies the schema and provides a useful display
name for the webpage object.