sparql PREFIX osmt: <https://wiki.openstreetmap.org/wiki/Key:> SELECT * WHERE { ?museum osmt:addr:city "New York"; osmt:tourism "museum"; osmt:wikidata ?wikidataID . }

cito--cites--1375511 says “this article CiTO:cites article 137511”.

Machine Tags

A new kind of tags — machine tags — are supported now. A machine tag, e.g. meta:language=python consists of a namespace (meta), a key (language) and a value (python). Everyone can created machine tags, but the meta: namespace is protected and tags in there will be created by the site itself.

The codesite itself uses machine tags to make various properties of recipes accessible to the search:

• meta:language

  The programming language of the recipe, e.g. python, perl or tcl.

• meta:min_$lang_$majorver

  Those tags describe the minimum language version. If a recipe requires Python 2.5 it would have the tag meta:min_python_2=5.

• meta:license

  The license that was selected by the author, e.g. psf, mit or gpl.

• meta:loc

  This tag contains a number describing the lines of code in a recipes. It counts only the number of lines in the code block but not any lines in the discussion of in comments. This makes it possible to search for short recipes with less than ten lines or very large ones.

• meta:score

  The current score of the recipe. This is the same number that is displayed besides the recipe title and can only be influenced by voting on recipes. That way you could even search for down-voted recipes

• meta:requires

  Stores information about additional requirements of the recipes, e.g. required python modules. You can find recipes using python's collections module that way.

All those tags cannot be changed directly because they are generated from a recipe's properties.

We also support machine tags that follow the pattern NAMESPACE:KEY=VALUE. For example: geo:lat=43.555 camel:size=medium machine:tag=with space Machine tags are not revealed to the user on the track pages.

• musicbrainz:artist=<MBID>
• musicbrainz:release=<MBID>
• musicbrainz:track=<MBID>
• musicbrainz:label=<MBID>

• astro:name=NGC 4565
• astro:orientation=11.73
• astro:RA=189.083922302

The metadata is structured. So structured that we can represent the example machine tags in a table:

<table> <thead><tr> <th style="text-align:center">namespace</th> <th style="text-align:center">predicate</th> <th style="text-align:center">value</th> </tr> </thead> <tbody> <tr> <td style="text-align:center">astro</td> <td style="text-align:center">name</td> <td style="text-align:center">NGC 4565</td> </tr> <tr> <td style="text-align:center">astro</td> <td style="text-align:center">orientation</td> <td style="text-align:center">11.73</td> </tr> <tr> <td style="text-align:center">astro</td> <td style="text-align:center">RA</td> <td style="text-align:center">189.083922302</td> </tr> </tbody> </table>

Or in a tree:

  astro
  |-- name
  |   `-- NGC 4565
  |-- orientation
  |   `-- 11.73
  `-- RA
      `-- 189.083922302