Skip to end of metadata
Go to start of metadata

Page Contents

EVN Assets


An asset is a technical, business, or operational resource governed by an organization using TopBraid EVN. Examples of assets could include documents, vocabulary terms and relationships, data schema and profiles, reference data, requirements, and other technical or enterprise resources.

Asset collection

Assets are organized into collections, which are stored technically as named graphs. Each asset collection has at least one manager. It can also have one or more users with the edit and view privileges. Asset collections have a variety of other metadata such as description, RACI, etc. Collections can include each other by reference. When editing information in one collection, users can see and link to any information in the included collection. They cannot, however, delete or change any information stored in the included collection.

Asset collection type (aka Project Type)

Each asset collection has exactly one type. It determines what kind of assets are stored in the asset collection, what kind of metadata (attributes and relationships) is captured about an asset collection and what functionality such as imports, exports, reports, editing applications, etc., are available for it. TopBraid EVN includes many project types such as Glossary, Reference Dataset, Lineage Model, Ontology, etc. Users can create their own project types.

Asset type

An asset can have one or more types. Asset type is a class in an ontology (either ontologies shipped with TopBraid EVN or customized/created by the users) that formally describes attributes and relationships of an asset. TopBraid EVN includes over 100 asset types such as Glossary Term, Database, Requirement, etc. Since asset type is a class in an ontology, depending on your perspective, it may also be an asset.

EVN Teamwork

The teamwork system maintains production and working copies of asset collections, along with change history, and role-based views and functions.


An object that can be created by a user to capture input, question or an issue with an asset, an asset collection or a task. Even if a user doesn’t have edit privileges for an asset collection, they can still create comments about assets described in the collection. Comments can have statuses.

Manager, Editor, Viewer (Teamwork roles)

These are sets of access control permissions that a user or a group of users (defined as LDAP/Active Directory group) may have for an asset collection's production copy or any of its working copies. A user’s access to asset collections is personalized according to their permissions. For example, users will only see asset collections for which they have at least a view level permission. Only managers of an asset collection will see its Manage view or be able to change access permissions of other users. Only editors will be able to modify information about an asset in an asset collection.

Production copy

The official version of an asset collection that is currently in use (cf. working copy).


An object that is created to capture a work item associated with an asset or an asset collection. A task has to have an assignee and a status. It may have a due date. It may also have comments.

Working copy

This is a branched copy of a production asset collection, which isolates its editing, review, and approval activities. A working copy may go through a workflow approval process, after which its changes may or may not be committed back into the official production version. There may be multiple simultaneous working-copy instances as users in various roles make and review changes in parallel.

EVN General


A copy of a resource with all its metadata. Creating and editing clones can be a useful way to create new resources with minimal data entry.

Core codelist

For user convenience, TopBraid EVN ships with some pre-built resources to be used as ranges of certain relationships. These are organized into core codelists  For example, assets and asset collections can have statuses and TopBraid EVN offers a list of possible status values for them. Users can extend these or replace them with their own preferred values. 


A change in data stored in TopBraid EVN that EVN is watching for and is prepared to act upon. 

Event type

Each event has exactly one Event Type. Event Type formally describes what data change indicates that event has occurred and what action TopBraid EVN should take when it happens e.g., send a notification e-mail. TopBraid EVN pre-defines several event types. For example, a change in a working copy status. Users can create additional event types.


Attribute (aka datatype property)

An attribute is a specific piece of information that you capture for a resource, such as a name or a short textual description. Each attribute has a range of values of some literal type (e.g., text, numbers, etc.) (cf. property, relationship).


The basic unit of a vocabulary. A concept is usually known by its preferred label, and can have various kinds of metadata assigned to it.

Concept type

A subset of a vocabulary's concepts grouped together for easier management. The concepts within a given type may themselves be grouped into subtypes of that type. Different concept types can have different custom attribute and relationship properties. Also known as a class.


A description of concepts in a business area. Ontologies can be combined using EVN's include and import features. An ontology is an information model.


An attribute or relationship associated with a given class or concept, such as its preferred label, broader and narrower concepts, and annotations such as scope notes (cf. attribute, relationship).

Range (of values)

A range defines what values are possible for a specific attribute or a specific relationship. Ranges for attributes are mainly standard XML datatypes such as string, integer and date. HTML datatype is also supported for storing rich text. Ranges for relationships are classes. For example, in case of the “column of” relationship between a Database Column and a Database Table, the range of relationship is the class Database Table.

Relationship (aka object property)

This is a directional link between exactly two resources. It captures how they are related to each other. Each relationship has a range of values (cf. property, attribute).


This is anything you want to capture information about using TopBraid EVN. Asset is a resource. Asset collection is a resource. Properties (attributes and relationships) are resources, etc. Each resource has a globally unique URI. Formally speaking, a resource is any object that is uniquely identifiable by a URI, a uniform resource identifier. It is used by the web infrastructure you are familiar with. URLs are URIs, as are e-mail addresses.


This is a set of concepts grouped together into a list or hierarchy. It might represent a taxonomy, a thesaurus, a code list, or any other controlled vocabulary. A vocabulary may be a single scheme, but because of EVN's ability to group several vocabularies together, some may appear as multiple schemes. For example, you might have a taxonomy of apparel products and another of colors in which the clothing was available both displayed at the same time.


A set of business concepts described using SKOS. These are typically used for taxonomies, vocabularies, or reference data that is hierarchical in nature.

  • No labels