[Data-modeling] Structured or typed weblinks?

[Bryan Cheung]

> Authorized Website
> Menu
> Exterior Photo
> Interior Photo
These properties are probably not good candidates for URI templating.   
I would suggest the ECT of /common/webpage.  You could have 1 or more  
properties represent these URLs (e.g. restaurant_webpage or  
auth_website, menu, photo_link).  When you go to add a weblink, there  
would be a new choice in the type dropdown called Restaurant Webpage  
which, if you chose that type, would assert that value to your property.

> Yelp
> OpenTable
> Boorah
These are probably good candidates for an enumeration/uri templating  
if the URI uses the foreign key in the URI as a url parameter. These  
would need to have single property each on your type (e.g. yelp_id,  
opentable_id, boorah_id).  When you enter the URL in the weblinks, the  
client will detect if it fits the URI template, and if it does, it  
will automatically add the key to the namespace that the property  
enumerates to.  At a quick glance, looks like Yelp and OpenTable seem  
like good candidates, and Boorah would require more examination of the  
dataset.

On Apr 12, 2009, at 1:19 PM, Don Jackson wrote:

>
> On Fri, Mar 20, 2009 at 11:37 AM, Christopher R. Maden
> <crism at metaweb.com> 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.
>
> This still sounds good.
>
> Does a template have to be used?  The issue in this case is that not
> all URIs I
> want to use will fit into any sort of structured template schema.
>
>> The question, then, is what rôles are desired for restaurant links?
>
> The roles I would initially propose for restaurants include:
>
> Authorized Website
> Menu
> Yelp
> OpenTable
> Boorah
> Exterior Photo
> Interior Photo
>
> Here are the values I would assign to those links for Manresa
> restaurant in Los Gatos:
>
> Authorized Website		http://manresarestaurant.com/
> Menu					http://manresarestaurant.com/menu/Menu.pdf
> Yelp					http://www.yelp.com/biz/manresa-restaurant-los-gatos
> OpenTable				http://www.opentable.com/rest_profile.aspx?rid=2026&ref=10003&ttr=1
>    (this might be ammenable to a template)
> Boorah					http://www.boorah.com/restaurants/CA/los-gatos/manresa-restaurant/3C09571953.html
>
>
> On Mar 20, 2009, at 10:06 AM, Tom Morris wrote:
>> The mechanism described by Chris is used for the U.S. National
>> Register of Historic Places and the Congressional Bioguide entries,
>> 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.  You  
>> can
>> see some examples at:
>>
>> http://www.freebase.com/view/en/ted_kennedy
>> http://www.freebase.com/view/en/washington_monument
>>
>> 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 have found the following references about this topic:
>
> 	http://www.freebase.com/view/en/creating_enumerated_properties
> 	http://www.freebase.com/view/en/creating_uri_templates
>
> But I'm not confident I understand how to implement what I want based
> on those entries.
>
> I'd appreciate some further advice or help!
>
> Don
>
>
>
>
>
>
>
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling