Main Page: Difference between revisions

From wikibase
Line 35: Line 35:
{{Q|66}} -> {{Q|804}} -> {{Q|801}}
{{Q|66}} -> {{Q|804}} -> {{Q|801}}


==== Proposed ====
==== Problem ====
 
For critical writings, we have a bunch of "types" (i.e. {{P|1}} items) that came from the ELMCIP Publication Type. For creative works we only have a few.
 
For creative works, ''all'' items are {{P|1}} {{Q|804}}. Any other {{P|1}} claims are added as an addition. For critical writings, they are only {{P|1}} their Publication Type. There is nothing linking them together.
 
We have a few options with downsides for each:


For critical writings, we have a bunch of "types" (i.e. {{P|1}} items) that came from the ELMCIP Publication Type. For creative writings we only have a few.
# Apply a standard {{P|1}} statement to ''all'' critical writings.
#; Use [https://www.wikidata.org/wiki/Q55915575 scholarly work (wikidata:Q55915575)]
#* Problem is that we would be assigning Wikidata items where they are not assigned in Wikidata
#; Create our own item like "critical writing"
#* Want to avoid custom items that aren't linked to Wikidata
# Create our own property like "Work Type"
#* Want to avoid custom properties that aren't linked to Wikidata
# Subclass critical writings with an item like "scholarly work" or a custom item like "critical writing"
#* Can't browse all critical writings. Have to use the Query Service.
# Track creative works and critical writings outside of the Wikibase (i.e. maintain a private list of what is what)
#* Our dataset can't be as easily reproduced by others


For creative works, ''all'' items are {{P|1}} {{Q|804}}. Any other {{P|1}} claims are added as an addition. For critical writings, they are only {{P|1}} their Publication Type. There is nothing linking them together. We should either add a new item like "scholarly work" or invent our own like "critical writing" and then either make all the critical-writing-related items a subclass of "scholarly work" or we add {{P|1}} "scholarly work" to every critical writing in addition.
==== Proposed ====


{{Q|66}} -> {{Q|804}} ->
{{Q|66}} -> {{Q|804}} ->

Revision as of 09:13, 21 January 2025

Links

Q Items

https://wikibase.cdn.uib.no/wiki/Special:AllPages?namespace=120

Properties

https://wikibase.cdn.uib.no/wiki/Special:ListProperties

DNKB Pages

https://wikibase.cdn.uib.no/wiki/Special:AllPages

Project Notes

Classification Items

Primary

Helper

Subclassed Items

Existing

work (Q66) -> literary work (Q802) -> electronic literature (Q801)

work (Q66) -> creative work (Q804) -> electronic literature (Q801)

Problem

For critical writings, we have a bunch of "types" (i.e. instance of (P1) items) that came from the ELMCIP Publication Type. For creative works we only have a few.

For creative works, all items are instance of (P1) creative work (Q804). Any other instance of (P1) claims are added as an addition. For critical writings, they are only instance of (P1) their Publication Type. There is nothing linking them together.

We have a few options with downsides for each:

  1. Apply a standard instance of (P1) statement to all critical writings.
    Use scholarly work (wikidata:Q55915575)
    • Problem is that we would be assigning Wikidata items where they are not assigned in Wikidata
    Create our own item like "critical writing"
    • Want to avoid custom items that aren't linked to Wikidata
  2. Create our own property like "Work Type"
    • Want to avoid custom properties that aren't linked to Wikidata
  3. Subclass critical writings with an item like "scholarly work" or a custom item like "critical writing"
    • Can't browse all critical writings. Have to use the Query Service.
  4. Track creative works and critical writings outside of the Wikibase (i.e. maintain a private list of what is what)
    • Our dataset can't be as easily reproduced by others

Proposed

work (Q66) -> creative work (Q804) ->

work (Q66) -> scholarly work (wikidata) ->

If the publication type was "Other" I used work (Q66).

If publication type was missing I used publication (Q48). This is confusing because "Book (Collection)" also uses publication (Q48).

Remove?

Wikidata Divergence

HTML

HTML (Q95) instance of (P1) programming language (Q7004)

Wikidata has HTML as a markup language which is a data description language which they specify as being opposite of a programming language.

The property programmed in requires items of type programming language or application programming interface. HTML is also a web API which is a subclass of application programming interface so it is allowed to be used with the programmed in property despite Wikidata specifically saying HTML is the opposite of a programming language.

This is the only case where we have a "programming language" that is not a "programming language." We want HTML to show up in our interfaces when users look for programming language items. The complexity is not worth it for us to distinguish between markup languages and programming languages. Thus we say that HTML is a programming language, even though Wikidata does not.