There's a traditional conflict in database design between "sparse" and
"dense" design, and that seems to be tied in with this problem. Personally,
I think I would go with the "sparse" design, which is to have individual
pages for the errors themselves. That way you wouldn't need to create a new
page for every episode, or even every scene of every episode. And you could
isolate exactly the information specific to each error.
To go with the original example, you could imagine a page titled "Error
#123" or, for more descriptiveness, "When did Bob meet Bill?" or some such.
It could then look like the following:
[[TV show::Bob and His Friends]] (...or does this wiki cover just one
show?...)
[[First episode::Episode 12]]
[[First scene:=Episode 12, Scene 3]]
[[Contradicting episode::Episode 92]]
[[Contradicting scene:=Episode 92, Scene 5]]
[[Character involved::Bob]]
[[Character involved::Bill]]
...some non-semantic text here, if you want to indicate exactly what
happened...
[[Category:Error]]
[[Category:Temporal error]]
-----------------------------
Note that I made episodes relations, and scenes attributes - I just can't
imagine you'd want pages for individual scenes (I could be wrong), but
having pages for episodes makes sense. Then each episode page could have at
least two queries, one for which subsequent episodes contradict it, and one
for which previous episodes it contradicts.
And "is-a" relationships are specified by categories; as S Page noted,
that's the current style; there are arguments for and against doing it that
way, but that seems to be the accepted way at the moment.
-Yaron
On 3/11/07, S Page <[EMAIL PROTECTED]> wrote:
(I removed [email protected] from follow-ups as I only know
about the Semantic MediaWiki extension, and no other semantic wiki
software.)
Kelly Jones wrote:
> I'd like to create a Semantic Wiki for continuity errors in a given TV
> series, and want suggestions on how best to do this.
>
> Each episode of the series has its own page. Let's say this error
> occurs in Episode 92:
>
> Bob's statement in scene 3 of this episode: "I knew Bill 10 years ago"
> contradicts the fact they met in scene 5 of "Episode 12: Bob Meets
> Bill", which took place only 4 years ago.
>
> The semantic relation here is:
>
> Episode 92 scene 3 :contradicts: Episode 12 scene 5
>
> How to best model this in SemanticWiki?
>
> My main goal: I don't want to put this continuity error in 2
> places. If I put it on Episode 92's page, I want it to automatically
> appear on Episode 12's page or vica versa.
Here's one approach:
1. Put the [[contradicts::name of later scene]] information on the first
scene's page.
2. Then, on each page, insert the following (it could be a template):
Here are a list of continuity errors with this scene described elsewhere
(continuity errors are described in the page for the ''first'' scene
with the error):
<ask>[[contradicts::{{PAGENAME}}]]</ask>.
The later scene will have a link to the first scene that describes the
error.
This is not ideal. E.g. the link to the first scene won't jump directly
to the description the continuity error. Your idea below to have a wiki
page for each continuity error may be better.
> Minor goal: I'd of course like to model:
>
> Episode 92 scene 3 :involves: Bob
> Episode 92 scene 3 :involves: Bill
> Episode 12 scene 5 :involves: Bob
> Episode 12 scene 5 :involves: Bill
Put [[Relation:Involves]] in each scene's page, and make a wiki page for
each character.
> Episode 92 scene 3 :is_a: temporal error
> Episode 12 scene 5 :is_a: temporal error
Often "is a" is relationships work better as a category, in this case a
Category:Temporal error subcategory of Category:Scenes with continuity
errors.
Or you could create Relation:Has continuity error, and put [[Has
continuity error::temporal error]] in the scene's page , and the
"temporal error" page could explain what a temporal continuity error is,
and provide an inline query that lists all scenes with this relation.
Or, you could not have this relation/category at all, and infer it by
querying for all pages that have particular kinds of error relationships.
You have lots of choices, try them all.
> The scenes are my "semantic objects", but I really don't want to
> create a page for each scene, especially if I end up deciding that
> each line of dialog is a "semantic object".
>
> I don't mind creating a page section (not a whole page) for each
> scene. Can SemanticWiki model relations between sections of pages?
Not Semantic *Media*Wiki as far as I know. The subject of both
relations and attributes is the thing described by the wiki page. Yours
is an interesting idea, but how would you indicate whether a predicate
is for a section or the wiki page as a whole? On your wiki you could
adopt a convention for this; but I think it would be fairly difficult to
hack the PHP code of SMW to track the current section as it parses and
present "Facts about scene 3... Facts about scene 5 ...".
To ease organization you could make the scenes subpages with a slash:
Episode_12/scene_5, Episode 92/scene 3. Mediawiki displays a breadcrumb
back to the top page, and there's a {{List subpages}} template on
Wikipedia that you can copy which lists all subpages. Note that by
default Mediawiki does not enable the subpage feature in the main
namespace; read http://meta.wikimedia.org/wiki/Sub-page#Administration
for the LocalSettings.php change that enables this.
> Another possibility is that each continuity error is a "semantic
> object" and I can say things like:
>
> Continuity error #517 ::involves:: Episode 92 scene 3
> Continuity error #517 ::involves:: Episode 12 scene 5
That is more powerful:
* allows you to describe the continuity error in one place that both
pages can link to
* allows you to cover the same continuity goof in more than two scenes
* makes a query that lists all continuity errors easy.
It also may feel more natural to say "This error is in category
``Continuity error''" than "These two scenes are in category ``Scenes
with continuity error''"
So it feels like a win to my little brain, but you have to decide if
it's worth having to create a third wiki page with a unique name for
each error.
> Any thoughts?
Hope you find these useful. I'm no expert.
FYI hardest-working person in wikibiz "Patrick" has created a lot of
test film pages on ontoworld.org such as the masterpiece
http://ontoworld.org/wiki/She%27s_the_Man ; alas ontoworld.org doesn't
have subpages enabled in the main namespace, so you and I can't try out
these ideas on scene subpages. I tried some of them in subpages of
http://ontoworld.org/wiki/User:Skierpage, but then you run into problems
with inline queries not including pages in the User: namespace.
--
=S Page
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Semediawiki-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/semediawiki-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Semediawiki-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/semediawiki-user
