Platform of Trust Platform Design Guide
Developer PortalAPI DocsOntology
  • Purpose and scope
  • Developer eXperience Strategy
  • Suggest changes
  • API Requests
    • Request validation
    • Response codes used
    • Error handling
  • General API guidelines
    • Performance
    • Documentation
    • Data models used
    • Use HATEOAS
    • Use HTTP Methods
    • Dates and time
    • Naming conventions
    • Pagination, partial response and sorting
    • API Testing
  • API Headers
    • Mandatory elements & behaviour
    • Rate limiting information
  • API Security
    • Authentication and authorization
    • SSL everywhere - all the time
  • API versioning guidelines
    • Versioning Rules
    • Breaking changes
    • Non-breaking changes example
    • Retirement process
    • Add new API to documentation
    • Add new endpoint
  • API Migration Policies
    • Deprecating API
    • Sunsetting API
    • Blackout Testing
    • Migration Email Template
    • API Blackout Test Email Template
    • API Deprecation Email
    • Deprecating an older API
  • Ontologies
    • About ontologies
    • Web Ontology Language, OWL
    • Ontology editor
    • Edit ontology
    • Add new subclass
    • Naming convention logic
    • Extending the ontology
  • Design Guideline
    • Colors
    • Typography
    • Grids and Space
    • Input forms - Text field
    • Input forms - Text area
    • Buttons
    • Checkbox
    • Radio buttons
    • Date picker
    • Form control - Single select
    • Toggle
    • Pagination
    • Status pills
    • Tables
    • Effects
    • Dialogues
Powered by GitBook
On this page

Was this helpful?

  1. Ontologies

Edit ontology

According to W3C principles and PoT guidelines

PreviousOntology editorNextAdd new subclass

Last updated 5 years ago

Was this helpful?

Opening PoT Core Ontology file with Protégé is easy. The editor is easy to use but you should know what you are doing. In general, you should be logical and consistent. These guides will get you started:

The W3C Web Ontology Language guide is here:

Ontology Development 101:

PoT guidelines for editing the ontology

DOs

  • Make increments. You can add new subclasses under the current classes. You can also add new properties.

  • Add missing annotations and refine existing ones.

  • Be logical and semantically consistent.

DON'Ts

  • Do not delete anything from the PoT Core Ontology. You are allowed to delete only the classes that you have added yourself.

  • Do not edit the class or property names of PoT Core Ontology. You are allowed to edit only the names of the classes you have added.

  • Do not change the types of relations between the current classes. You are allowed to change only the relation types of the classes you have added.

If any of the above restrictions is not followed, it may cause a breaking change.

https://www.w3.org/TR/owl-guide/
https://protege.stanford.edu/publications/ontology_development/ontology101.pdf