Definitions of Locator Types and Extensions #174
-
|
Hello, I'm wondering what's the source of truth (i.e., code definition) for Locator Types and Extensions in OASF: https://schema.oasf.agntcy.org/objects/locator?extensions= / https://schema.oasf.agntcy.org/features?extensions= If I look at Locators, in OASF I see this json (https://github.com/agntcy/oasf/blob/main/schema/objects/locator.json), that does not really match the types in the online schema above (see Also, if I look at the .proto file defined in agntcy/dir (https://github.com/agntcy/dir/blob/main/api/proto/core/v1alpha2/locator.proto#L17), I see that:
Can someone clarify/help? Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Hi @mtrinell, currently there is a slight difference between the locator types in OASF and Directory and we are aware of this. Starting from the v0.4.0 OASF release planned for this week, these two values should be identical and all the OASF-related objects in Directory will be imported directly from OASF. From there, the validation and other ops should work out-of-box. |
Beta Was this translation helpful? Give feedback.
The list of all the currently supported extensions can be found here: https://schema.oasf.agntcy.org/features
Each extension name is defined as part of a given feature, ie.
extension_name = schema.oasf.agntcy.org/features/<feature>.If you open a specific feature like https://schema.oasf.agntcy.org/features/observability, you can find the extension name there. Hope this helps.