<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"
  >
  


  <author ><name>popstra</name>
<uri>http://www.freebase.com/view/user/popstra</uri>
</author>



<generator uri="http://www.freebase.com/" >Freebase Atom Feed Generator</generator>


<id>http://popstra.freebase.com/</id>

<link href="http://www.freebase.com/feed/discuss/all/base/popstra" rel="self"  />





<title>Freebase: Discussion about popstra</title>

<updated>2009-12-22T16:18:47Z</updated>

<entry >
      <author ><name>jack</name>
<uri>http://www.freebase.com/view/user/jack</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;There is an app currently used as a demo that depends on some specific schema, www.popstra.com. There are no developer resources to make changes to the app at this time.&lt;/p&gt;
&lt;p&gt;So backward compatibility is still important for the owner of popstra and he doesn't want the sww_base properties (heat...) to be public. The plan was for those properties to be locked. &lt;/p&gt;
&lt;p&gt;The provenance issue was a core requirement. Unfortunately the schema development was based on a non-freebase repository and time did not permit creating new schema when the switch was made to freebase. &lt;/p&gt;
&lt;p&gt;It seems like the real issue is whether anyone plans to add lots of new data. The Popstra base has not been actively tended to for months. Does someone want to give it the love it deserves? If so, I'm sure the original creator of popstra would accommodate.&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f800000001309a174</id>

    <link title="popstra: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f800000001309a174" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >There is an app currently used as a demo that depends on some specific schema, www.popstra.com....</summary>

    <title>popstra: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-22T00:56:58.0009Z</updated>

</entry>
<entry >
      <author ><name>jack</name>
<uri>http://www.freebase.com/view/user/jack</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;There is an app currently used as a demo that depends on some specific schema, www.popstra.com. There are no developer resources to make changes to the app at this time.&lt;/p&gt;
&lt;p&gt;So backward compatibility is still important for the owner of popstra and he doesn't want the sww_base properties (heat...) to be public. The plan was for those properties to be locked. &lt;/p&gt;
&lt;p&gt;The provenance issue was a core requirement. Unfortunately the schema development was based on a non-freebase repository and time did not permit creating new schema when the switch was made to freebase. &lt;/p&gt;
&lt;p&gt;It seems like the real issue is whether anyone plans to add lots of new data. The Popstra base has not been actively tended to for months. Does someone want to give it the love it deserves? If so, I'm sure the original creator of popstra would accommodate.&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f800000001309a174</id>

    <link title="Celebrity: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f800000001309a174" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >There is an app currently used as a demo that depends on some specific schema, www.popstra.com....</summary>

    <title>Celebrity: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-22T00:56:58.0009Z</updated>

</entry>
<entry >
      <author ><name>bkn</name>
<uri>http://www.freebase.com/view/user/bkn</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;There is an app currently used as a demo that depends on some specific schema, www.popstra.com. There are no developer resources to make changes to the app at this time.&lt;/p&gt;
&lt;p&gt;So backward compatibility is still important for the owner of popstra and he doesn't want the sww_base properties (heat...) to be public. The plan was for those properties to be locked. &lt;/p&gt;
&lt;p&gt;The provenance issue was a core requirement. Unfortunately the schema development was based on a non-freebase repository and time did not permit creating new schema when the switch was made to freebase. &lt;/p&gt;
&lt;p&gt;It seems like the real issue is whether anyone plans to add lots of new data. The Popstra base has not been actively tended to for months. Does someone want to give it the love it deserves? If so, I'm sure the original creator of popstra would accommodate.&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013099cdb</id>

    <link title="popstra: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013099cdb" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >There is an app currently used as a demo that depends on some specific schema, www.popstra.com....</summary>

    <title>popstra: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-22T00:56:09.0021Z</updated>

</entry>
<entry >
      <author ><name>bkn</name>
<uri>http://www.freebase.com/view/user/bkn</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;There is an app currently used as a demo that depends on some specific schema, www.popstra.com. There are no developer resources to make changes to the app at this time.&lt;/p&gt;
&lt;p&gt;So backward compatibility is still important for the owner of popstra and he doesn't want the sww_base properties (heat...) to be public. The plan was for those properties to be locked. &lt;/p&gt;
&lt;p&gt;The provenance issue was a core requirement. Unfortunately the schema development was based on a non-freebase repository and time did not permit creating new schema when the switch was made to freebase. &lt;/p&gt;
&lt;p&gt;It seems like the real issue is whether anyone plans to add lots of new data. The Popstra base has not been actively tended to for months. Does someone want to give it the love it deserves? If so, I'm sure the original creator of popstra would accommodate.&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013099cdb</id>

    <link title="Celebrity: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013099cdb" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >There is an app currently used as a demo that depends on some specific schema, www.popstra.com....</summary>

    <title>Celebrity: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-22T00:56:09.0021Z</updated>

</entry>
<entry >
      <author ><name>bkn</name>
<uri>http://www.freebase.com/view/user/bkn</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;There is an app currently used as a demo that depends on some specific schema, www.popstra.com. There are no developer resources to make changes to the app at this time.&lt;/p&gt;
&lt;p&gt;So backward compatibility is still important for the owner of popstra and he doesn't want the sww_base properties (heat...) to be public. The plan was for those properties to be locked. &lt;/p&gt;
&lt;p&gt;The provenance issue was a core requirement. Unfortunately the schema development was based on a non-freebase repository and time did not permit creating new schema when the switch was made to freebase. &lt;/p&gt;
&lt;p&gt;It seems like the real issue is whether anyone plans to add lots of new data. The Popstra base has not been actively tended to for months. Does someone want to give it the love it deserves? If so, I'm sure the original creator of popstra would accommodate.&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013099abf</id>

    <link title="popstra: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013099abf" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >There is an app currently used as a demo that depends on some specific schema, www.popstra.com....</summary>

    <title>popstra: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-22T00:55:47.0025Z</updated>

</entry>
<entry >
      <author ><name>bkn</name>
<uri>http://www.freebase.com/view/user/bkn</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;There is an app currently used as a demo that depends on some specific schema, www.popstra.com. There are no developer resources to make changes to the app at this time.&lt;/p&gt;
&lt;p&gt;So backward compatibility is still important for the owner of popstra and he doesn't want the sww_base properties (heat...) to be public. The plan was for those properties to be locked. &lt;/p&gt;
&lt;p&gt;The provenance issue was a core requirement. Unfortunately the schema development was based on a non-freebase repository and time did not permit creating new schema when the switch was made to freebase. &lt;/p&gt;
&lt;p&gt;It seems like the real issue is whether anyone plans to add lots of new data. The Popstra base has not been actively tended to for months. Does someone want to give it the love it deserves? If so, I'm sure the original creator of popstra would accommodate.&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013099abf</id>

    <link title="Celebrity: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013099abf" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >There is an app currently used as a demo that depends on some specific schema, www.popstra.com....</summary>

    <title>Celebrity: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-22T00:55:47.0025Z</updated>

</entry>
<entry >
      <author ><name>jeff</name>
<uri>http://www.freebase.com/view/user/jeff</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;I second both of Phil's concerns. The first is addressable by simply moving the properties we want to keep to the commons Celebrity type, and leaving the rest on the Popstra one; as long as we kept the old property keys, legacy queries should still work.  The second is rather more problematic, since the properties in question are on CVTs. If backward-compatibility is needed with the original Popstra model, I'm not sure what to do with those properties.&lt;/p&gt;
&lt;p&gt;There's also another issue that many of the properties denormalize properties on other types: religion (although the primary religion property [on the Person type] is not date-mediated) and endorsements for sure, and possibly some others.  These would have to be migrated, but again, if backward-compatibility is important, it may be problematic.&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f800000001305dbcb</id>

    <link title="popstra: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f800000001305dbcb" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I second both of Phil's concerns. The first is addressable by simply moving the properties we want...</summary>

    <title>popstra: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-21T21:59:18.0009Z</updated>

</entry>
<entry >
      <author ><name>jeff</name>
<uri>http://www.freebase.com/view/user/jeff</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;I second both of Phil's concerns. The first is addressable by simply moving the properties we want to keep to the commons Celebrity type, and leaving the rest on the Popstra one; as long as we kept the old property keys, legacy queries should still work.  The second is rather more problematic, since the properties in question are on CVTs. If backward-compatibility is needed with the original Popstra model, I'm not sure what to do with those properties.&lt;/p&gt;
&lt;p&gt;There's also another issue that many of the properties denormalize properties on other types: religion (although the primary religion property [on the Person type] is not date-mediated) and endorsements for sure, and possibly some others.  These would have to be migrated, but again, if backward-compatibility is important, it may be problematic.&lt;/p&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f800000001305dbcb</id>

    <link title="Celebrity: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f800000001305dbcb" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I second both of Phil's concerns. The first is addressable by simply moving the properties we want...</summary>

    <title>Celebrity: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-21T21:59:18.0009Z</updated>

</entry>
<entry >
      <author ><name>pak21</name>
<uri>http://www.freebase.com/view/user/pak21</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;-1 for promoting this in its current form. There's the basis of a good schema here, but this isn't it yet. I raised a number of issues in &lt;a href=&quot;http://lists.freebase.com/pipermail/data-modeling/2009-November/002416.html&quot;&gt;this mail&lt;/a&gt;, none of which seem to have been addressed. More generally:&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;There seem to be a mixture of application-specific properties (&quot;heat&quot;, &quot;interest&quot;) and general properties in the types - promoting the latter makes sense, but I think the former should stay out of the commons.&lt;/li&gt;
&lt;li&gt;Do we want to go down the route of having every property being a CVT with source and date? I think everyone acknowledges data provenance is an issue, but I'm not convinced this is the right solution.&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013031c19</id>

    <link title="popstra: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013031c19" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >-1 for promoting this in its current form. There's the basis of a good schema here, but this isn't...</summary>

    <title>popstra: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-20T23:00:59.0006Z</updated>

</entry>
<entry >
      <author ><name>pak21</name>
<uri>http://www.freebase.com/view/user/pak21</uri>
</author>

    
    <content type="html">&lt;div&gt;&lt;p&gt;-1 for promoting this in its current form. There's the basis of a good schema here, but this isn't it yet. I raised a number of issues in &lt;a href=&quot;http://lists.freebase.com/pipermail/data-modeling/2009-November/002416.html&quot;&gt;this mail&lt;/a&gt;, none of which seem to have been addressed. More generally:&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;There seem to be a mixture of application-specific properties (&quot;heat&quot;, &quot;interest&quot;) and general properties in the types - promoting the latter makes sense, but I think the former should stay out of the commons.&lt;/li&gt;
&lt;li&gt;Do we want to go down the route of having every property being a CVT with source and date? I think everyone acknowledges data provenance is an issue, but I'm not convinced this is the right solution.&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013031c19</id>

    <link title="Celebrity: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013031c19" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >-1 for promoting this in its current form. There's the basis of a good schema here, but this isn't...</summary>

    <title>Celebrity: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-20T23:00:59.0006Z</updated>

</entry>
<entry >
      <author ><name>robert</name>
<uri>http://www.freebase.com/view/user/robert</uri>
</author>

    
    <content type="html">&lt;p&gt;I support it as well, as I originally created the commons celebrity type and acknowledge the clear superiority of the popstra ones. &lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013031941</id>

    <link title="popstra: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013031941" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I support it as well, as I originally created the commons celebrity type and acknowledge the clear...</summary>

    <title>popstra: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-20T22:36:44.0013Z</updated>

</entry>
<entry >
      <author ><name>robert</name>
<uri>http://www.freebase.com/view/user/robert</uri>
</author>

    
    <content type="html">&lt;p&gt;I support it as well, as I originally created the commons celebrity type and acknowledge the clear superiority of the popstra ones. &lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000013031941</id>

    <link title="Celebrity: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000013031941" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I support it as well, as I originally created the commons celebrity type and acknowledge the clear...</summary>

    <title>Celebrity: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-20T22:36:44.0013Z</updated>

</entry>
<entry >
      <author ><name>robert</name>
<uri>http://www.freebase.com/view/user/robert</uri>
</author>

    
    <content type="html">&lt;p&gt;I support it as well, as I originally created the commons celebrity type and acknowledge the clear superiority of the popstra ones.&lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f800000001303192c</id>

    <link title="popstra: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f800000001303192c" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I support it as well, as I originally created the commons celebrity type and acknowledge the clear...</summary>

    <title>popstra: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-20T22:36:31.0000Z</updated>

</entry>
<entry >
      <author ><name>robert</name>
<uri>http://www.freebase.com/view/user/robert</uri>
</author>

    
    <content type="html">&lt;p&gt;I support it as well, as I originally created the commons celebrity type and acknowledge the clear superiority of the popstra ones.&lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f800000001303192c</id>

    <link title="Celebrity: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f800000001303192c" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >I support it as well, as I originally created the commons celebrity type and acknowledge the clear...</summary>

    <title>Celebrity: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-20T22:36:31.0000Z</updated>

</entry>
<entry >
      <author ><name>doconnor</name>
<uri>http://www.freebase.com/view/user/doconnor</uri>
</author>

    
    <content type="html">&lt;p&gt;+1 to this happening?&lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f800000001303182e</id>

    <link title="popstra: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f800000001303182e" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >+1 to this happening? </summary>

    <title>popstra: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-20T22:29:54.0014Z</updated>

</entry>
<entry >
      <author ><name>doconnor</name>
<uri>http://www.freebase.com/view/user/doconnor</uri>
</author>

    
    <content type="html">&lt;p&gt;+1 to this happening?&lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f800000001303182e</id>

    <link title="Celebrity: Promote /popstr/celebrity to Commons?" href="http://www.freebase.com/view/guid/9202a8c04000641f800000001303182e" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >+1 to this happening? </summary>

    <title>Celebrity: Promote /popstr/celebrity to Commons?</title>

    <updated>2009-12-20T22:29:54.0014Z</updated>

</entry>
<entry >
      <author ><name>becky2987</name>
<uri>http://www.freebase.com/view/user/becky2987</uri>
</author>

    
    <content type="html">&lt;p&gt;An article in the August 24 issue of In Touch linked Melissa Joan Hart and her family's recent move to Connecticut to her mother Paula's recovery from brain tumor surgery. However, Paula still lives in Malibu, where she's recovering nicely! &lt;/p&gt;</content>

    
    <id>http://www.freebase.com/view/guid/9202a8c04000641f8000000012892c5a</id>

    <link title="Paula Hart: Melissa's mom: Feeling much better!" href="http://www.freebase.com/view/guid/9202a8c04000641f8000000012892c5a" rel="alternate" type="text/html"  />


    
    
    
    <summary type="html" >An article in the August 24 issue of In Touch linked Melissa Joan Hart and her family's recent move...</summary>

    <title>Paula Hart: Melissa's mom: Feeling much better!</title>

    <updated>2009-12-11T02:04:39.0006Z</updated>

</entry>
</feed>
