[Data-modeling] Structured or typed weblinks?

[Don Jackson]

On Mar 20, 2009, at 8:37 AM, Christopher R. Maden wrote:

> The Freebase data model allows specific roles to be assigned to
> weblinks; this is done by creating a property with a URI value or a
> template.
>
> See, for example, the IMDb link for a film, TV show, actor, or  
> character.
>
> The question, then, is what rôles are desired for restaurant links?

This is very helpful!

Here are some of the roles I can imagine:

1) "Organization-Authorized-Website" (or something like that!)
      This is not restaurant specific at all.
       Seems like for any topic that is about some entity/org that has  
its own
	web site, the link for that web site should be included and typed as  
per something like this.

2) "Menus"
	This would be a link to the restaurant's menu.
	Of course, an HTML version of the menu would be ideal, but a lot of  
restaurants
	 don't have their own web site, and one can imagine scanning their  
menu, and providing a link
	 to the resulting PDF.  Of course, if the restaurant does have their  
own website, and on it
	 provides their menu, then this entry would be direct link to the  
menu on their own web site

3) "Photos"
	Not restaurant specific.  Photos of the topic

4) "Yelp"
	Link to the Yelp page on this restaurant/business-establishment
	I'm sure there are other Yelp-like directories that people would like  
to include....
  	when we figure out what those are, we can add them also.
	"OpenTable might be another good one here.

5) "Reservations"
	Link to online reservation page for restaurant.
	In some/many cases this may be a link into OpenTable (if that is the  
chosen reservation method of restaurant)

6) "News/Blog"
      Link to blog/news about restaurant.

7) "Review"
	Link to a specific article/review of restaurant.
	For example, a newspaper review, eg The New York Times.

Thoughts/comments/suggestions????


On Mar 20, 2009, at 10:06 AM, Tom Morris wrote:

> but one limitation to be aware of is that it currently only allows for
> a single URL to be displayed for each entry.

> Also, since the template
> is tied to an enumeration, no two restaurants can share the URL.  They
> must all be unique in the namespace used for the enumeration.

Interesting!  As I look through the examples I offered above, this  
limitation seems like it might not be a problem.
>
> If you're interested in pursuing this approach, there are cookbook
> entries for modeling the enumeration and the URI template, but you'll
> need to do some of the enumeration setup through the explore/explore2
> views since the schema editor no longer supports the method described
> in the cookbook.


I am interested, but I don't yet understand the above.  I will poke  
around and see
if I can figure it out on my own, if not, I'll ask for help.

Don