Computer Game Version from CVT to Standard
-
-
It seems like it might be beneficial to change the display type of Computer Game Version from Combined to Standard, for a few reasons:
- Computer Game Version topics can be co-typed with "Consumer product" and "Software" when appropriate.
- The number of properties being proposed for Computer Game Version is quickly growing (Peripherals supported, Distributed through, etc.) and I can think of many more than can apply to a version and not the whole game, content (ESRB, CERO) ratings, for one.
- There are a few properties that exist for Computer Game that can have different content for different versions (platform exclusive characters come to mind.)
-
I think it makes sense; it would bring the Computer Game/Release model more into line with the Book/Book Edition and Album/Release models.
-
I've no problem with moving Computer Game Version from a CVT to a normal topic (one other advantage would be that we could lose the slightly hacky "Version specific name" field from Computer Game Version), but I think that potential co-typing with Software could open a fairly large can of worms. We've essentially got two parallel sets of types for modelling some of this, one in /cvg and one in /computer: compare Compare Game Developer and Software Developer, release dates on both Computer Game (Version) and Software, and Computer Game Platform and Operating System are also very similar. How are we going to handle the almost-but-not-quite duplicated data this could produce?
-
You're right, there is quite a bit of overlap. I was just throwing out some possibilities. Personally, I'm not as worried about co-typing with "Software" as I am with "Consumer product".
-
If this does go through, I think the to-do list would look something like this:
- Migrate Version-Specific Name to Name
- Change Computer Game Version from CVT to Standard
- Deprecate Version-Specific Name
- Delete Version-Specific Name
-
I'm not sure that deleting Version-Specific name is necessary; that will cause queries to fail and I don't really see the need if it's hidden, but I'll bow to those with greater expertise on this one.
Other than that, will "we" need to cotype every current instance of Computer Game Version as a topic? If so, I suspect that's probably best done internally by someone at Metaweb.
-
Hiding "version specific name" and changing the property hint to say that it's deprecated is a solution that's been used before.
Co-typing as /common/topic can be done by Metaweb; just create a JIRA task when you're ready and assign it to "Freebase Commons and Schema."
I can't think of any other tasks for this. It's a pretty big change, so I'd recommend running it past the developers and data-modelers lists, especially since we're deprecating a field. (I wouldn't expect changing something to a standard type to break anything, but you never know what people will try.)
-
So:
- Migrate Version-Specific Name to Name
- Change Computer Game Version from CVT to Standard
- Co-type all Computer Game Version instances to "/common/topic"
- Deprecate Version-Specific Name
-
+5
-
One additional step:
- For all instances where there is no version-specific name, copy Name of the parent program to Name
-
Jira tasked: DA-871
-
