BeameryBeamery

Concepts

Conceptual models and schemas that define the structure and relationships of taxonomy elements in the Beamery platform

Overview

The Concepts section contains detailed models and schemas that define how various taxonomy elements are structured, related, and processed within the Beamery ecosystem. These models provide the foundation for understanding and working with skills, roles, and other taxonomic concepts.

URI Scheme

Entities

Entity URI path structure attempts to follow this hierarchy:

  • authority (e.g. company, standards body)
    • dataset
      • entity type(s)
        • entity ID
          • sub-entity type(s) (optional)
            • sub-entity ID (optional)

Based on that, a common URI template looks like this: https://data.beamery.com/{Authority}/{Dataset}/{EntityType}/{EntityID}

Non-information resources (real-world objects, abstract concepts etc.) get a #this fragment identifier to distinguish them from documents containing their descriptions (see Topic Relation).

Below you can find URI examples for different types of sources and entities.

Ontologies

<https://data.beamery.com/beamery/model/ontologies/talent#> a owl:Ontology .
<https://data.beamery.com/beamery/model/ontologies/talent#Skill> a owl:Class .
<https://data.beamery.com/beamery/model/ontologies/talent#hasSkill> a owl:ObjectProperty .

Taxonomies

Canonical

<https://data.beamery.com/beamery/bkg-v3/skills#this> a skos:ConceptScheme .
<https://data.beamery.com/beamery/bkg-v3/skills/123456789#this> a skos:Concept .

Customer

<https://data.beamery.com/salesforce/job-architecture/roles#this> a skos:ConceptScheme .
<https://data.beamery.com/salesforce/job-architecture/roles/123456789#this> a skos:Concept .

Named graphs

Canonical

Same as entity URI, except without the fragment identifier. These can also serve as Linked Data document URLs from which entity descriptions (e.g. HTML or RDF) can be dereferenced.

Example

<https://data.beamery.com/pdl/person-data/persons/2908fe2b-f718-493c-8f86-1a74e6241031> { ... }
<https://data.beamery.com/pdl/person-data/companies/10b02366-e598-4f4b-b0c6-faba41c7013b> { ... }

Aspect

Parts of entity description may be stored in (e.g. per-datasource) aspect graphs.

<https://data.beamery.com/pdl/person-data/people/2908fe2b-f718-493c-8f86-1a74e6241031/experiences> { ... }

Provenance

Provenance graphs are meta-graphs (named graphs with metadata about entity named graphs), therefore they follow their own URI structure https://data.beamery.com/graphs/{UUID}.

<https://data.beamery.com/graphs/28446e09-1fd0-4564-826b-1e0fcab02103> { ... }

Delta

A special kind of provenance graphs that contain added/removed triples. They follow their own URI structure https://data.beamery.com/delta/{UUID}

<https://data.beamery.com/delta/4fa5f3f7-74a1-498b-8c41-81a8a44d9060> { ... }

Available Models

Skill

The Skill provides a comprehensive JSON-LD schema for representing skills, including their properties, relationships, proficiency levels, and contextual information. This model supports both human-readable and machine-processable skill data.

Role

The Role provides a comprehensive JSON-LD schema for representing professional roles using SKOS vocabulary. This model includes multilingual support, semantic relationships, and connections to skills, abilities, and work activities.

Seniority Level

The Seniority Level model provides a hierarchical JSON-LD schema for representing professional seniority levels using SKOS vocabulary. This model includes collections for grouping related seniority levels and supports organizational hierarchy representation.

Job Family Group

The Job Family Group model provides a comprehensive JSON-LD schema for representing job family collections and their relationships using SKOS vocabulary. This model includes collections for grouping related job families and supports job architecture organization.

Job Family

The Job Family model provides a detailed JSON-LD schema for representing individual job families using SKOS vocabulary. This model includes comprehensive definitions, relationships, and connections to other taxonomic concepts.

Future Models

Additional conceptual models will be added here as the taxonomy system evolves, including:

  • Industry Model
  • Competency Model
  • Learning Path Model

Integration

These conceptual models integrate with:

  • Taxonomy API: For managing taxonomic concepts
  • Skills Management: For operational skill management
  • Analytics: For skill-based insights and reporting
  • Job Architecture: For role and task associations

Supported Languages

All conceptual models provide comprehensive multilingual support:

Supported Languages

  • English (en): Primary language for all labels and definitions
  • Spanish (es): Spanish translations
  • French (fr): French translations
  • German (de): German translations
  • Extensible: Additional languages can be added as needed

Label Types

  • prefLabel: Primary/preferred name for concepts
  • altLabel: Alternative names and common variations
  • hiddenLabel: Search terms not displayed to users
  • skos:definition: Comprehensive descriptions of concepts

Schema Standards

All conceptual models follow these standards:

  • JSON-LD: Semantic markup for linked data
  • SKOS: Simple Knowledge Organization System vocabulary
  • Schema.org: Structured data vocabulary
  • Dublin Core: Metadata standards

For detailed implementation examples and usage patterns, refer to the individual model documentation.