Difference between revisions of "Help:To Do"

From CanonBase
 
(One intermediate revision by the same user not shown)
Line 13: Line 13:
 
**significant equipment (P89) ''' decided to keep
 
**significant equipment (P89) ''' decided to keep
 
**is accessory of (P128) ''' Done
 
**is accessory of (P128) ''' Done
** has hosted performance of (P126)  
+
** has hosted performance of (P126) ''' Done
  
 
* check "tags" what is now "see also" property if it should be mentions"
 
* check "tags" what is now "see also" property if it should be mentions"
Line 28: Line 28:
 
* clarify equipment - generic - type - unique piece
 
* clarify equipment - generic - type - unique piece
 
** we need to clarify the relation between unique piece, type and the higher levels of generic descriptions, but that is for later.  
 
** we need to clarify the relation between unique piece, type and the higher levels of generic descriptions, but that is for later.  
But I think a division between generic types, that have a [subclass of] property, types that are not clearly defined, but could have a new property [type of], and the unique pieces that have only a [type of equipment] as qualifier in the [type of information] could make it easier to define visualisations?)
+
** But I think a division between generic types, that have a [subclass of] property, types that are not clearly defined, but could have a new property [type of], and the unique pieces that have only a [type of equipment] as qualifier in the [type of information] could make it easier to define visualisations?)
  
 
== expected value lists ==
 
== expected value lists ==

Latest revision as of 11:19, 19 August 2023

Help index


Properties

  • clean out inverse properties
    • author of (inverse property label of author, P41)
    • has designed building (inverse property label of architect P48) Done
    • has published (inverse property label of publisher P62) Done
    • has invented (inverse property label of inventor (P267)) Done
    • has designed equipment (inverse property of designer, P225) Done
    • has manufactured (inverse property label of manufacturer, P49) Done
    • is mentioned in (inverse property label of mentions, P78) Done
    • was significant person for (P87) Done
    • significant equipment (P89) decided to keep
    • is accessory of (P128) Done
    • has hosted performance of (P126) Done
  • check "tags" what is now "see also" property if it should be mentions"
  • create inverse property label
    • create inverse property label of [related property] with label "has value list" in properties.
  • New properties
    • light source (candle, gas, Lime, (Open) arc, incandecent, halogen, Discharge)
    • Check properties from Gerriets list
    • specific property for logo
      • child of internal picture
  • clarify equipment - generic - type - unique piece
    • we need to clarify the relation between unique piece, type and the higher levels of generic descriptions, but that is for later.
    • But I think a division between generic types, that have a [subclass of] property, types that are not clearly defined, but could have a new property [type of], and the unique pieces that have only a [type of equipment] as qualifier in the [type of information] could make it easier to define visualisations?)

expected value lists

  • improve copyright expected value list (with commons statements)

Queries

Visualisations

interoperability

  • Check theatres with Lodepa
  • Check theatre company with Lodepa

Wikidata