Manage Cookie Consent

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies in the "Privacy Statement" link.

We also use third-party cookies that help us analyse how you use this website, store your preferences, and provide the content that is relevant to you. These cookies will only be stored in your browser with your prior consent.

Please note that disabling such cookies may affect your browsing experience.

Agriculture Product Types Ontology (APTO)
OWL
Last submission date March 20, 2025

General information

The Agriculture Product Types Ontology (APTO) is an ontology of types, meaning it does not contain individuals and is intended as a classification system for agricultural commodities price index databases in Brazil. This ontology contains labels and comments in both Portuguese and English. There are two main modules: :Organism and :Product_type. The :Organism class contains subclasses that represent the taxonomy of species related to the production of given product types. It imports taxonomic information from the Global Biodiversity Information Facility (GBIF) Backbone Taxonomy via API. The :Product_type class has six main subclasses organized into major groups: :Inorganic_compound :Animal_product :Plant_product :Raw_product :Processed_product :By-product The :Animal_product and :Plant_product classes include subclasses indicating the type of processing the product has undergone. These subclasses are also children of :Raw_product, :Processed_product, and :By-product. Object Properties APTO defines nine object properties: :has_ingredient and :is_ingredient_of (inverse properties): Indicate that a product type is used in the manufacturing of a processed product type (e.g., :Cow_cheese :has_ingredient :Cow_milk). :derives_from and :derives_in (inverse properties, imported from the Relations Ontology (RO)): Indicate that a product type originates from another product type (e.g., :Cocoa_almond :derives_from :Cocoa). :member_of_taxon (imported from the Biological Collections Ontology (BCO)): Indicates that an organismal entity belongs to a taxon (e.g., :Pacu :member_of_taxon :Piaractus_mesopotamicus). :produced_by and :produces (inverse properties, imported from RO): Indicate that an organismal entity produces a given type of product. For example, :Assai :produced_by :Assai_palm, and :Assai_palm :member_of_taxon :Euterpe_oleracea. If only the final product is listed in commodity databases and the rest of the organism holds no commercial value, the product is linked directly to the taxon (e.g., :Pineapple :produced_by :Ananas_comosus). :residue_of: Indicates that a by-product is the residue of manufacturing another product (e.g., :Whey :residue_of :Cheese). :is_a_hybrid_of: Specific to the :Organism subclasses, indicating a hybrid of two species (e.g., :Citrus_aurantium :is_a_hybrid_of ( :Citrus_reticulata and :Citrus_maxima ))., meaning it does not contain individuals and is intended as a classification system for agricultural commodities price index databases in Brazil. This ontology contains labels and comments in both Portuguese and English. There are two main modules: :Organism and :Product_type. The :Organism class contains subclasses that represent the taxonomy of species related to the production of given product types. It imports taxonomic information from the GBIF Backbone Taxonomy via API. The :Product_type class has six main subclasses organized into major groups: :Inorganic_compound :Animal_product :Plant_product :Raw_product :Processed_product :By-product The :Animal_product and :Plant_product classes include subclasses indicating the type of processing the product has undergone., meaning it does not contain individuals and is intended as a classification system for agricultural commodities price index databases in Brazil. This ontology contains labels and comments in both Portuguese and English. There are two main modules: :Organism and :Product_type. The :Organism class contains subclasses that represent the taxonomy of species related to the production of given product types. It imports taxonomic information from the Global Biodiversity Information Facility (GBIF) Backbone Taxonomy via API. The :Product_type class has six main subclasses organized into major groups: :Inorganic_compound :Animal_product :Plant_product :Raw_product :Processed_product :By-product The :Animal_product and :Plant_product classes include subclasses indicating the type of processing the product has undergone.
Initial created on October 15, 2024. For additional information, contact Filipi Soares (filipivgp2011@gmail.com).

Categories and subjects

Product Types
Ontology
Agriculture


Metrics

We have not yet calculated metrics for APTO

FAIR score
Beta

We could not collect the data from the fairness service

Semantic resource relations network

View of (bpm:viewOf) ×
Imports(omv:useImports) ×
Has equivalences with(door:isAlignedTo) ×
Generally related to or relies on(door:ontologyRelatedTo) ×
Backward compatible(omv:isBackwardCompatibleWith) ×
Incompatible(omv:isIncompatibleWith) ×
Comes from the same domain(door:comesFromTheSameDomain) ×
Similar to(door:similarTo) ×
Specializes(door:explanationEvolution) ×
Generalizes(voaf:generalizes) ×
Disparate modelling with(door:hasDisparateModelling) ×
Has part (has views)(dct:hasPart) ×
Used by(voaf:usedBy) ×
Translation(schema:workTranslation) ×
Translation of(schema:translationOfWork) ×

Submissions

Version
Modified Submitted
Actions

1.31

March 7, 2025 March 20, 2025

Identifiers

URI

https://w3id.org/APTO#
https://w3id.org/APTO#
Loading

EcoPortal URI

http://ecoportal.lifewatch.eu/ontologies/APTO
http://ecoportal.lifewatch.eu/ontologies/APTO
Loading

Visits

Views of APTO

No views available for APTO.

ID https://w3id.org/APTO#Product_type
https://w3id.org/APTO#Product_type
http://ecoportal.lifewatch.eu/ontologies/APTO/Product_type
Loading
Preferred name
No preferred name for selected language.
Subject Author Type Created
No notes to display
Subject Author Type Class Created
No notes to display
OBOE161FABIO117LUPO46DSW65ECSO520MR34STY89SFWO793BCO509INBIO997CMECS212EURIO95PCO516DCSO43FOVT1948FOS59EUROVOC10915ENVTHES2412
Add APTO Web Widgets to your site
Jump To

Type a class name from APTO and jump to it in EcoPortal

  • Download the quick_jump.js file and put it on your server.
  • Copy the code below and paste it to your HTML page
  • Note: If you would like to use Quick Jump across multiple semantic resources
    • You can enter a comma-separated list of semantic resource ids
      var BP_ontology_id = "NCIt,SNOMEDCT";
    • You can set the variable to 'all' to search all semantic resources in EcoPortal:
      var BP_ontology_id = "all";
  • To include definitions in the Jump To drop-down, add the following variable in Javascript:
    var BP_include_definitions = true;
  • In the code that you just pasted, make sure to change the path to the quick_jump.js file to point to the location where you put the file (relative to your HTML file)
    • For example, if you put the quick_jump.js file in the same directory as your HTML file, this is the code you would use:
      <div id="bp_quick_jump"></div>
                  <script type="text/javascript">
                      var BP_ontology_id = "APTO";</script>
                  <script src="quick_jump.js" type="text/javascript" charset="utf-8"></script>
      

For more help visit NCBO Widget Wiki


Autocomplete

Fill your form fields with classes from APTO

Example 1 (start typing the class name to get its full URI)

Example 2 (get the ID for a class)

Example 3 (get the preferred name for a class)

  • Download the form_complete.js file and put it on your server.
  • In the header for the page where you want the form field, include the form_complete.js In the header for the page where you want the form field, include the
  • On your form, for the fields where you want to use the class-selection widget, specify the field's class in the following format: bp_form_complete-{ontology_id_list}-{value}
    • For example, bp_form_complete-NCIT-uri will use NCI Thesaurus (semantic resource id is NCIT) and will put the class URI in the field after the user selects the class from the pull-down list.
      • Note: In addition to single semantic resource ids, you can use a list:
        bp_form_complete-NCIT,NCBITAXON-uri
      • OR use 'all' to search across all EcoPortal semantic resources:
        bp_form_complete-all-uri
      • The autocomplete widget accesses semantic resource content from the latest version of the semantic resource.
    • You can use the following parameters to select which value will be placed into the user-visible input field:
      • uri Put the complete URI of the class (e.g., http://aims.fao.org/aos/agrovoc/c_8115 )
      • shortid put the short id of the class, as used in EcoPortal (e.g., "Common_Neoplasm");
      • name put the preferred name of the class (e.g., "Common Neoplasm");
  • In addition to the input element you defined, there are four hidden form elements that are created and then set when a user selects a class from the list. For example, if you create a field with this code:
      <input type="text" name="a" class="bp_form_complete-all-uri" size="100"/>
    The 'name' attribute is used to create the four following fields (note how the 'a' from the name attribute is appended to the id attribute):
    • <input type="hidden" id="a_bioportal_preferred_name">
    • <input type="hidden" id="a_bioportal_concept_id">
    • <input type="hidden" id="a_bioportal_ontology_id">
    • <input type="hidden" id="a_bioportal_full_id">
    • Additional parameters are documented on the NCBO Widget Wiki

    For more help visit NCBO Widget Wiki


    Visualization

    Display a visualization for a given class in APTO

    Copy the code below and paste it to your HTML page

    <iframe frameborder="0" src="/widgets/visualization?ontology=APTO&class=http%3A%2F%2Faims.fao.org%2Faos%2Fagrovoc%2Fc_8115&apikey=YOUR_API_KEY"></iframe>
    

    For more help visit NCBO Widget Wiki


    Tree Widget

    Display a class tree with a search field for APTO

    • Loading...
    Copy the code below and paste it to your HTML page

    <link rel="stylesheet" type="text/css" href="/widgets/jquery.ncbo.tree.css">
      <script src="/widgets/jquery.ncbo.tree-2.0.2.js"></script>
      <div id="widget_tree"></div>
      var widget_tree = $("#widget_tree").NCBOTree({
        apikey: "YOUR_API_KEY",
        ontology: "APTO"
      });
    
    

    You can also view a detailed demonstration

    For more help visit NCBO Widget Wiki