The RDF Toolkit deals with a number of concepts, a model of how ontologies are serialized and "built" or "published" including the derived products. All these Concepts are modelled in the Artifact Ontology which will be the "Configuration File" for the RDF Toolkit.

Product
- Product - schema.org — The FIBO schema.org http://schema.org Ontology, published here: https://spec.edmcouncil.org/fibo/schema.org/ https://spec.edmcouncil.org/fibo/schema.org/
- Product - simf — TODO: Dean Allemang
- Product - vocabulary — The FIBO Vocabulary, published here: https://spec.edmcouncil.org/fibo/vocabulary/ https://spec.edmcouncil.org/fibo/vocabulary/
- Product - ontology — The FIBO OWL Ontologies, published here: https://spec.edmcouncil.org/fibo/ontology https://spec.edmcouncil.org/fibo/ontology
- Product - site — The overall FIBO product documentation as published on https://spec.edmcouncil.org/FIBO, which includes the documentation for all other products.
Builder — A Builder is a process that takes the source artifacts for one given Product and generates all the publishable artifacts for that Product.
Source — todo
Serialization Format — The Artifacts that the RDF-Toolkit can generate can have all sorts of formats, also called serialization formats. For OWL ontologies for instance we have serialization formats like RDF/OWL, JSON-LD and Turtle.
- OWL/XML — The "XML serialization for OWL 2 https://www.w3.org/TR/owl2-xml-serialization/," which is an alternative exchange syntax for OWL 2 (alternative to RDF/XML).
- Manchester Syntax
- RDF/XML — RDF/XML is a serialization format that can be used to serialize ANY graph of RDF statements, not just OWL ontologies. It has no specific support for OWL ontologies and is therefore considered to be hard to read and understand.
Class — TODO
Module — TODO
Artifact Model
Artifact — An artifact is the specification of a physical piece of information that is used or produced by a software development process https://en.wikipedia.org/wiki/Software_development_process, or by deployment and operation of a system.
Encoding — todo
Commit — todo
Version — todo
View — A User Interface construct showing a specific subset of information
- Glossary View — TODO (Business User View)
Product Family
Ontology — TODO
Domain — A Domain in the EDM Council context is usually a Domain in the Financial Industry.
Branch — The term "Branch" is taken from Git. Branches are used to separate multiple tracks of development with different levels of maturity of the work on the artifacts in that track.
Reasoning Level — For certain types of Artifacts that are being generated by the RDF Toolkit, it can be relevant to apply "reasoning" via a "reasoner" or "inference engine" in memory before writing out the Artifacts.

Browser not supported