So, with Harry Potter on my mind (I have already finished reading Book 7 but promise no spoilers in this message) - I went to explore the character topic for him. I realized that there are lots of things revealed in book 7 that could result in many bits of meta data being populated in his character record... but these bits of data would give away things that happen in the final book. Anyone else have opinions about metadata as spoilers?
How awful would it be if you had just seen Star Wars and looked up the character Luke Skywalker -only to see the list of who his father and sister are? (And yes.. I just checked and they are both populated). Does it make sense to imagine specific attributes that might be hidden by default and displayed only on demand if the user requests them? I am likely being overly paranoid - but I hope there are sympathetic ears out there...
Metadata as spoiler?
-
-
-
I think it comes down to what we want freebase to be. Considering that freebase.com is a vehicle (a very fancy one) for the data that is stored in the Metaweb and not a domain specific application, my personal preference would be to display everything. I could definitely see a film based application that would not display spoiler information and would allow the user to choose whether or not (s)he wants to view the information.
That said, a spoiler property on film, TV show and book types would go a long way towards facilitating the development of the example application I mention above and in implementing a 'spoiler warning' functionality. -
Could we add a new type that then permitted you to add the list of attributes that contained spoiler data? That type could then be added to any topic, and the list of spoiler attributes could be populated and used by developers as they see fit.
If there were a way to group attributes assigned to a topic in various ways - that might work too.
Other ideas? -
A spoiler type sounds like good idea. I would encourage you to model the type in your own domain and then once you are satisfied with the schema, let one of the domain admins of the file domain know about.
Regarding grouping of attributes that are 'contained' by a type, the way its usually done is to create a compoud value type and then adding a property to the 'container' type, whose type is the CVT.
HTH
-
