I'm learning RDF/metadata/XML etc. Using Protege to help build an ontology for a film: things like actors, producers, budget, genre need to be included.
I think I have made 1 big mistake though.
My class higherarchy is something like:
All semed nice and logical. Now it was a biut more advanced with a MiscInformation subclass, and lots more subclasses in TechnicalInformation and MovieInformation etc. And I made classes for things like language which has two strings, the spoken and the subtitled language, Genre was enumerated to different types etc.
All looked well and good until I read some information that said that the class hierarchy strictly follows a "Is A" relations ship, or an "Instance Of" relationship. Well My main subclasses such as TechnicalInformation are not instances of Film and they are not "a kind of Film". Therefore I guess these should be represented as slots or properties of the Film superclass. Fine, but now my lovely higherarchy really isn't a higherarchy- its a single class with 4-5 property fiels eahc of which are instances of a class containg information.
The example I'm reading uses wines, e.g. redwine, white, chardony etc. And so one can make an easy hierarchy first by dividing by colour, and then gregion/grape/purpose etc. But doing this with films make so sense, e.g. having subclasses for each genre, then splitting them up and so on so forth.
Am I completely off track or is what I have done sensible>
I think I have made 1 big mistake though.
My class higherarchy is something like:
Code:
Film
People TechnicalInformation MovieInformation
Cast Crew Language Format Runtime Genre Description Tile
listofActors crew "eng" "widescreen" 238 "fantasy" "...." "LOTR"All semed nice and logical. Now it was a biut more advanced with a MiscInformation subclass, and lots more subclasses in TechnicalInformation and MovieInformation etc. And I made classes for things like language which has two strings, the spoken and the subtitled language, Genre was enumerated to different types etc.
All looked well and good until I read some information that said that the class hierarchy strictly follows a "Is A" relations ship, or an "Instance Of" relationship. Well My main subclasses such as TechnicalInformation are not instances of Film and they are not "a kind of Film". Therefore I guess these should be represented as slots or properties of the Film superclass. Fine, but now my lovely higherarchy really isn't a higherarchy- its a single class with 4-5 property fiels eahc of which are instances of a class containg information.
The example I'm reading uses wines, e.g. redwine, white, chardony etc. And so one can make an easy hierarchy first by dividing by colour, and then gregion/grape/purpose etc. But doing this with films make so sense, e.g. having subclasses for each genre, then splitting them up and so on so forth.
Am I completely off track or is what I have done sensible>