Caution! This site is PROVISIONAL and provided for purposes of EVALUATION ONLY.

URI Service

Why URIs for statistical classifications

In all statistical classifications we can distinguish a terminology and a coding system. Statisticians are usually mostly interested in the coding part, as codes are what is used in tables and databases to serve as dimensions of the data. Codes are more practical then names, as they are (usually much) shorter and easier to manipulate in a database. However, codes alone do not ensure that data is unambiguously described, as the "meaning" of a code is only defined within the scope of the classification it belongs to - once extracted from its classification of origin, a code is ambiguous, at best, if not meaningless altogether.  In this sense, codes are "local" entities, and raise interpretation issues when passing data from one system to another. Moreover, also the terminological part plays a crucial role in statistical classifications. 

Caliper aims at making the sharing of statistical classifications as smooth, unambiguous and interoperable as possible. To this end, it provides classifications and items with unique identifiers over the web, aka URI (Unique Resources Identifiers). A local code is then paired with an URI that allows one to unambiguously identify it - always and everywhere. URIs are a especially useful for machines (computer applications), as they can access the corresponding web address  (URL) and retrieve all relevant information associated to the item (in a language that machines can process automatically). Humans may also access those web addresses and see a simple page showing the same information accessed by a machine, but more nicely visualized, suitable for human reading. This mechanism of serving data differently depending on who access the web address, is called "content negotiation", a standard and well established web technique. Caliper implements content negotiations through Loddy, an open source software powered by the University of Tor Vergata. 

For example, the URI* for "wheat" in WCA is "http://stats-class.fao.uniroma2.it/WCA/crops/Wheat". That URL will resolve in different ways depending on "who" access it. To a machine, it will appear as just a bunch of RDF statement, while if you use it your browser (say Firefox, Chrome or IE), you will see this page:

Loddy
A classification's item in Loddy

The tool we use to render the RDF into an HTML page is Loddy.

Try the following URLs:

URIs for concept schemes

Some users may find useful to have the full list of URIs concept schemes currently included in Caliper (run this query to get always the current ones)

 "http://stats-class.fao.uniroma2.it/geo/m49fao/

 "http://stats-class.fao.uniroma2.it/ISIC/rev4/scheme
 "http://stats-class.fao.uniroma2.it/CPC/v2.1/core
 "http://stats-class.fao.uniroma2.it/ICC/v1.0/scheme
 "http://stats-class.fao.uniroma2.it/CPC/v2.1/ag
 "http://stats-class.fao.uniroma2.it/ICC/v1.1/scheme
 "http://stats-class.fao.uniroma2.it/WCA/crops/scheme
 "http://stats-class.fao.uniroma2.it/CPC/v2.0/scheme
 "http://stats-class.fao.uniroma2.it/CPC/v2.1/fert
 "http://stats-class.fao.uniroma2.it/FCL/v2019/scheme
 "http://stats-class.fao.uniroma2.it/HS/fao_mapping_targets/scheme
 "http://stats-class.fao.uniroma2.it/WRB/v1998/scheme
 "http://stats-class.fao.uniroma2.it/foodex2/all
 "http://stats-class.fao.uniroma2.it/geo/M49/SDG-groups
 "http://stats-class.fao.uniroma2.it/geo/M49/FAO/current
 "http://stats-class.fao.uniroma2.it/geo/M49/FAO/2019-12
 "http://stats-class.fao.uniroma2.it/geo/M49/FAO/2019-07
 "http://stats-class.fao.uniroma2.it/geo/M49
 "http://stats-class.fao.uniroma2.it/FPCD/v2016/scheme
 "http://stats-class.fao.uniroma2.it/caliper-catalog/scheme
 "http://stats-class.fao.uniroma2.it/CRS/v2016_05/sector_purpose/scheme
 "http://stats-class.fao.uniroma2.it/CRS/v2018_01/sector_purpose/scheme
 "http://stats-class.fao.org.uniroma2.it/CRS/v2020_01/sector_purpose
 "http://stats-class.fao.uniroma2.it/WRB/v2014/qualifiers

 "http://stats-class.fao.uniroma2.it/WRB/v2014/rsg

 "http://data.food.gov.uk/codes/foodtype/hierarchy/main/botanic
 "http://data.food.gov.uk/codes/foodtype/hierarchy/main/biomo
 "http://data.food.gov.uk/codes/foodtype/hierarchy/main/expo
 "http://data.food.gov.uk/codes/foodtype/hierarchy/main/feed
 "http://data.food.gov.uk/codes/foodtype/hierarchy/main/pest
 "http://data.food.gov.uk/codes/foodtype/hierarchy/main/report
 "http://data.food.gov.uk/codes/foodtype/hierarchy/main/vetdrug
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/alcohol
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/animage
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/cookExt
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/cookMeth
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/dough
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/fat
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/fort
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/fpurpose
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/gen
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/gender
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/ingred
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/legis
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/medium
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/packFormat
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/packMat
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/part
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/partCon
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/place
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/prep
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/preserv
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/process
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/prod
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/qual
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/racsource
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/replev
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/riskIngred
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/state
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/sweet
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/targCon
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/treat
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/use
 "http://data.food.gov.uk/codes/foodtype/hierarchy/facet/source

 

(*) NOTE that, being Caliper an experimental service, not yet an official service of FAO, these URI are subject to change. They should not yet be used as reference.