Skip to content

Releases: agntcy/oasf

Release v0.8.1

08 Dec 20:55
v0.8.1
7978e5d

Choose a tag to compare

What's Changed

Full Changelog: v0.8.0...v0.8.1

Release v0.7.2

08 Dec 20:55
v0.7.2
2b4b9df

Choose a tag to compare

What's Changed

Full Changelog: v0.7.1...v0.7.2

Release v0.8.0

22 Oct 13:22
v0.8.0
5801a13

Choose a tag to compare

New Features

  • Expanded domain taxonomy. Added 15 new root domain categories (legal, agriculture, energy, media_and_entertainment, real_estate, hospitality_and_tourism, telecommunications, environmental_science, government_and_public_sector, research_and_development, retail_and_ecommerce, social_services, sports_and_fitness, insurance, marketing_and_advertising) and created 88 new subdomain JSON files with standardized descriptions and UID constraints. (#343) by @muscariello

  • Extended skill taxonomy. Added 8 new top-level skill categories (UIDs 8–15) including security_privacy, data_engineering, agent_orchestration, evaluation_monitoring, devops_mlops, governance_compliance, tool_interaction, and advanced_reasoning_planning, with 40+ initial leaf skills to improve capability→skill mapping. (#338) by @muscariello

  • Agent Spec feature extension. Added support for Open Agent Spec configuration in OASF records, enabling developers to export assistant configurations and load them into different AI Agent frameworks (Langgraph, Autogen, CrewAI, WayFlow) for seamless framework switching. (#334) by @paul-cayet

  • Customizable map type. Introduced typed_map_t type in the dictionary allowing values to be any dictionary type (with string keys for valid JSON), replacing the more restrictive string_map_t for enhanced flexibility in annotations and other map-based fields. (#331) by @akijakya

  • Base object support. Added base object to OASF protos enabling encoding of any OASF-defined object into a protobuf Object type, providing explicit differentiation between OASF and non-OASF objects across gRPC APIs. (#293) by @ramizpolic

  • Enhanced UI improvements. Improved entity and graph UI with better class and object pages, enhanced graph view that displays subclasses when loading a class, and added card view option on classes pages for better visualization. (#311) by @akijakya

  • More informative validation errors. Enhanced class validation error messages to include specific attribute paths (e.g., skills[3], domains[1]) instead of generic error locations, significantly improving debugging experience. (#335) by @akijakya

  • Sample generator improvements. Enhanced sample generator to avoid returning duplicate entries and improved overall data quality in generated samples. (#300) by @akijakya

Changed

  • Class categories API restructuring. ⚠️ Breaking Change ⚠️ Renamed main_skills → skill_categories and similar endpoint changes, bumping the API version. This provides clearer API structure but requires updates to existing integrations. (#323) by @akijakya

  • Module reorganization. Deprecated Manifest module and reorganized modules into new module categories with improved organization and clearer structure. (#324) by @akijakya

  • Signature field flexibility. Made some signature fields optional to provide more flexibility in record definitions and reduce validation constraints where appropriate. (#306) by @akijakya

  • OASF acronym correction. Fixed "Agents" to "Agentic" in OASF acronym for consistency and accuracy. (#288) by @akijakya

Fixed

  • Extension support improvements. Fixed sample generator, UI, JSON schema generator, and validator to properly handle entities added via extensions, ensuring full compatibility with custom extensions. (#321) by @akijakya

  • Validator input handling. Fixed validator error when input is not a map, now properly handles different input types and provides appropriate error responses. (#297) by @akijakya

  • Schema version display. Fixed display of schema_version to show without "v" prefix for consistency across the system. (#319) by @akijakya

  • Deprecated class filtering. Fixed sample generator to exclude deprecated classes from generated samples, ensuring only current and valid classes are included. (#327) by @akijakya

Other

  • Protobuf version support. Added v0.3.1 proto files under the types folder for enhanced version compatibility. (#292) by @adamtagscherer

  • CI/CD improvements. Added git diff logging when format is checked, server compilation tests, JSON schema formatting checks, and more verification jobs to improve code quality and reliability. (#339), (#309), (#336), (#280) by @arpad-csepi, @akijakya

  • Documentation updates. Updated documentation with docs site improvements and enhanced contributing guide. (#308) by @akijakya

  • Technology domain expansion. Added more Technology domain categories to provide better coverage of technology-related domains. (#326) by @akijakya

  • Protobuf namespacing fixes. Resolved protobuf namespacing issues to ensure proper compilation and compatibility. (#304) by @ramizpolic

  • API testing. Added comprehensive API tests to improve reliability and catch regressions. (#294) by @akijakya

  • Version management. Adjusted versions post v0.7.0 release and bumped schema and server version to 0.8.0. (#287), (#5801a13) by @akijakya

New Contributors

Full Changelog: v0.7.0...v0.8.0

Release v0.7.1

17 Sep 09:44
v0.7.1
a1275d2

Choose a tag to compare

What's Changed

  • fix: validator, generator, signature object by @akijakya in #307

Full Changelog: v0.7.0...v0.7.1

Release v0.3.3

17 Sep 09:52
v0.3.3
707272a

Choose a tag to compare

What's Changed

Full Changelog: v0.3.2...v0.3.3

Release v0.7.0

05 Sep 11:36
v0.7.0
b508a64

Choose a tag to compare

New Features

  • Enum object validation. The system now properly validates enum objects (such as domain and skill) that are identified by the is_enum: true property in the OASF schema dictionary (oasf/schema/dictionary.json). Previously, validation for these enumerated objects was bypassed, but the validator now correctly identifies and validates values against the appropriate object definitions defined in the dictionary. (#258) by @akijakya
  • Improved children object/class display. Enhanced the server's ability to display children objects and classes with better formatting and more detailed information for easier debugging and development workflows. (#282) by @akijakya
  • New types folder structure. Created new types/ folder specifically for v1alpha1 proto files, replacing the deprecated objects/ folder. This provides better organization and clearer separation of protocol buffer definitions by version, enabling more maintainable code structure and easier version management. (#263) by @akijakya

Changed

  • Extensions-to-modules terminology update. ⚠️ Breaking Change ⚠️ Records that conform to v0.7.0 must now use "modules" rather than "extensions" in the record object. This provides greater clarity and eliminates previous confusion regarding record extensions being termed "features" in OASF. This change affects both API structure and requires updates to existing records and documentation. (#263,#284) by @akijakya
  • Simplified module class structure. Removed version from feature classes since module versions are tied to the OASF schema version, and added optional id to module classes for uniform referencing across all class families (skills, domains, etc.). The optional id is particularly useful when using schema extensions, as calculated ids differ for classes from extensions. (#263) by @akijakya
  • Record object simplification. Removed schema_url from the record object as the directory now starts with an OASF instance in the configuration. The oasf-sdk uses generated and downloaded JSON Draft-07 schemas by version for record validation. (#263) by @akijakya
  • Base class removal. Removed base_class and references from schema and server components to simplify the inheritance model and reduce complexity. (#273) by @akijakya
  • Schema adjustments and ACP attribute prefixing. Added acp_ prefixes to attributes coming from Manifest feature class to improve naming consistency and prevent conflicts. Also included various small fixes to schema handling. (#263) by @akijakya
  • Validator support for optional IDs across all class types. Added validator support for the presence of optional id in all class types (skills, domains, and modules), enabling uniform identification across the OASF schema. The validator also implements logic to skip validation for modules not found in OASF, enabling custom modules while maintaining validation for standard OASF modules. (#265) by @akijakya

Fixed

  • Validator error handling. Fixed validator 500 response on incorrect input, now returns appropriate error codes instead of server errors for better user experience and debugging. (#262) by @akijakya
  • Schema type issues. Resolved schema type inconsistencies between schema and server components to ensure proper data validation and processing. (#272) by @akijakya

Other

Full Changelog:
v0.6.0...v0.7.0

Release v0.6.1

05 Sep 11:29
v0.6.1
c123198

Choose a tag to compare

What's Changed

Full Changelog: v0.6.0...v0.6.1

Release v0.5.3

05 Sep 11:29
v0.5.3
913535d

Choose a tag to compare

What's Changed

  • backport: adjust record requirements in 0.5.0 by @akijakya in #286

Full Changelog: v0.5.2...v0.5.3

Release v0.6.0

13 Aug 13:27
v0.6.0
898776d

Choose a tag to compare

Overview

This release adds several important features:

  • New schema for MCP servers and A2A cards
  • Improvements to the record object with new references to OASF via schema_url and domains properties
  • (breaking change) Removal of schema URL prefix from names of skills, domains, and feature objects
  • UI improvements and feature porting from OCSF
  • Server bug fixes for schema generation and validation

What's Changed

New Contributors

Full Changelog: v0.5.0...v0.6.0

Release v0.5.2

13 Aug 13:31
v0.5.2
3ada6d2

Choose a tag to compare

What's Changed

Full Changelog: v0.5.1...v0.5.2