Wikidata:WikiProject Digital Narratives

From Wikidata
Jump to navigation Jump to search

Scope

[edit]

The goal of this project is to develop approaches to documenting digital narratives such as electronic literature (Q173167), narrative video game (Q7889), AI-generated narratives, VR narratives, and social media narratives. The WikiProject is initiated by researchers at Center for Digital Narrative (Q124428748).

Resources

[edit]

Relevant Wikidata projects

[edit]

Models and Ontologies

[edit]

Websites that sync with wikidata

[edit]

Tools

[edit]

Tasks

[edit]

Properties

[edit]

See Wikidata:WikiProject Digital Narratives/Properties

Subpages

[edit]

Participants

[edit]
[+] Add yourself to the list

The participants listed below can be notified using the following template in discussions:
{{Ping project|Digital Narratives}}

You may add the participants' template on your userpage: {{User Digital Narratives}}.

Discussion Topics

[edit]

How to handle software specific properties?

[edit]

Take a look at this work of e-lit: Game, game, game, and again game (Q115534333)

It has the following flagged properties:

The flag on programmed in (P277) is triggered because the item must be an instance or subclass of:

The flag on software engine (P408) is triggered because the item must be an instance of subclass of:

Now technically, video game is a subclass of software. So for Game, game, game, and again game (Q115534333) we can just add instance of (P31) video game (Q7889) which is true and solves the problem. But that is not a universal solution. Not all works of electronic literature are video games.

We have 3 options:

1. Edit the item electronic literature (Q173167) to make it a subclass of a qualifying type.

2. Edit the properties programmed in (P277) and software engine (P408) to allow electronic literature (Q173167).

3. Do both.

4. Manually assign a seperate (but qualifying) instance of (P31) to every one of the thousands of creative works we have.

I am very hesitant to suggest editing the properties to make an exception for just e-lit. It would be better if we could define e-lit in a way that indicates its electronic nature. Right now it is only a subclass of literary work (Q7725634) which has nothing to do with computers.

But is it accurate to say that all electronic literature is software? I don't think so. We could say that e-lit is both a subclass of publication by electronic means (Q15938550) and program code (Q124590) but can we really say that all electronic literature is program code? Technically electronic literature is defined in Wikidata as "requiring digital computation" so doesn't that make it program code?

What about an alternative where we redefine both electronic literature (Q173167) and programmed in (P277)/software engine (P408)? For example, we say that electronic literature (Q173167) is a subclass of digital content (Q11320476) and that digital content (Q11320476) should be an allowed constraint type for programmed in (P277) and software engine (P408).


Thank you for writing this up, Colin.
My first instinct is to say: not all electronic literature is software or a videogame, but perhaps all e-lit with a programmed in (P277) property can be counted as software (Q7397) or program code (Q124590) and all e-lit using a software engine (P408) can be an instance of video game (Q7889) in addition to electronic literature (Q173167).
I also like the final solution of e-lit as a subclass of digital content (Q11320476) as an allowed constraint type for programmed in (P277) and software engine (P408).
HanAck (talk) 09:11, 2 December 2024 (UTC)[reply]
I like the solution of adding a special instance of (P31) when we have those properties. But for software engine (P408) the value is often things like Adobe Flash (Q165658) - so not always video games. For example, These Waves of Girls (Q114609969) uses Flash as the software engine. But I guess we could tag everything with software engine (P408) as a publication by electronic means (Q15938550). Or what about defining electronic literature (Q173167) as an instance of a publication by electronic means (Q15938550)? --Colin R Robinson (talk) 09:40, 2 December 2024 (UTC)[reply]
I think electronic literature (Q173167) as an instance of publication by electronic means (Q15938550) makes the most sense. All electronic literature works are literary works published by electronic means. Many contemporary works will also be an instance of online publication (Q1714118) but this won't be the case for every one.
This way we also avoid some (in my opinion) erroneous categorisations of Adobe Flash (Q165658) works as video games. Witscrafft (talk) 10:51, 2 December 2024 (UTC)[reply]
I agree with @Witscrafft that all electronic literature (Q173167) can be an instance of publication by electronic means (Q15938550). And if, as I think Colin is saying, we can loop back so that if an instance of electronic literature (Q173167) has the properties programmed in (P277) or software engine (P408) then we add that it is an instance of program code (Q124590) - that seems like it would solve the problem? Lijil (talk) 14:14, 2 December 2024 (UTC)[reply]
Yes, but I will use software (Q7397) instead of program code (Q124590). And when the property programmed in (P277) is specifically HTML (Q8811) or JavaScript (Q2005) or PHP (Q59) then I will instead use web page (Q36774) which is a subclass of software (Q7397). Colin R Robinson (talk) 08:40, 3 December 2024 (UTC)[reply]
[edit]

The description of references work, tradition or theory (P8371) is: "creative work, tradition or theory this creative work references by allusion, quote or similar means (for citations in scholarly and legal works use cites work (P2860)"

I think that we have agreed to only add statements linking from critical writing to creative works and not put any statements on the creative works. So we should alway use cites work (P2860) and never references work, tradition or theory (P8371).

Good catch, Colin. HanAck (talk) 13:44, 3 December 2024 (UTC)[reply]