Wikidata:Property proposal/Computer Science Ontology topic

From Wikidata
Jump to navigation Jump to search

CSO topic id[edit]

Originally proposed at Wikidata:Property proposal/Authority control

   Done: CSO topic ID (P11334) (Talk and documentation)
DescriptionComputer Science Ontology topics: automatically generated taxonomy of research topics in the field of Computer Science. Link only to preferentialEquivalent topics!
RepresentsComputer Science Ontology (Q104843592)
Data typeExternal identifier
Domainitem
Allowed values[a-z0-9_()%.-]+
Example 1Semantic Web (Q54837) -> semantic_technologies, semantic_technology, semantic_web_applications, semantic_web_technologies, semantic_web_technology
Example 2computer-aided design (Q184793) -> computer_aided_design_%28cad%29 (or computer_aided_design_(cad), cad
Example 3artificial intelligence (Q11660) -> artificial_intelligence
Example 4computer vision (Q844240) -> computer_vision
Sourcehttps://cso.kmi.open.ac.uk/
Planned usemake a mix-n-match catalog from CSV download at https://cso.kmi.open.ac.uk/downloads
Number of IDs in source14000
Expected completenesseventually complete (Q21873974)
Implied notabilityWikidata property for an identifier that suggests notability (Q62589316)
Formatter URLhttps://cso.kmi.open.ac.uk/topics/$1
See alsoACM Classification Code (2012) (P2179)
Applicable "stated in"-valueComputer Science Ontology (Q104843592)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectWikiProject Informatics (Q115651894), WikiProject Ontology (Q60005226)

Motivation[edit]

An important resource for people working with computer science research, by Open University and SpringerNature.

  • Also includes formatter for RDF resource: https://cso.kmi.open.ac.uk/topics/$1.ttl
  • Can serve per-entity RDF, JSON, and other formats
  • One item will often link to multiple CSO topics (which themselves are linked by relatedEquivalent), see first two examples
  • Maybe I'm blind but I couldn't find a previous proposal for this

Vladimir Alexiev (talk) 16:30, 12 December 2022 (UTC)[reply]

I updated the examples to show that CSO topics really are labels. But they are connected through relatedEquivalent, and the main label is designated as preferentialEquivalent. You can see that eg in https://cso.kmi.open.ac.uk/topics/semantic_technologies.ttl
  <https://cso.kmi.open.ac.uk/topics/semantic_technologies> 
    ns0:relatedEquivalent <https://cso.kmi.open.ac.uk/topics/semantic_web_technology> , <https://cso.kmi.open.ac.uk/topics/semantic_web_technologies> ,                 <https://cso.kmi.open.ac.uk/topics/semantic_web_applications> , <https://cso.kmi.open.ac.uk/topics/semantic_web> , <https://cso.kmi.open.ac.uk/topics/semantic_technology> ;
    ns0:preferentialEquivalent <https://cso.kmi.open.ac.uk/topics/semantic_web>
So: we should link only to preferential topics, and use the others as alt labels. I've tweaked the proposal to show this.
I also changed the name to "CSO topic id" as per User:SM5POR below Vladimir Alexiev (talk) 14:10, 14 December 2022 (UTC)[reply]
I included "%" in the regex because some topic URLs use percent encoding (eg computer_aided_design_%28cad%29).
While https://cso.kmi.open.ac.uk/topics/computer_aided_design_(cad).ttl is more readable and resolves, the semantic data inside uses the percent-encoded form of URL. Vladimir Alexiev (talk) 15:29, 14 December 2022 (UTC)[reply]

Discussion[edit]