fix: broken oasf links

docs/dir/dir-record-example.md

@@ -212,15 +212,15 @@
           ]
         }
       },
-      "name": "schema.oasf.agntcy.org/features/runtime/framework",
+      "name": "schema.oasf.outshift.com/features/runtime/framework",
       "version": "v0.0.0"
     },
     {
       "data": {
         "type": "python",
         "version": ">=3.9,<4.0"
       },
-      "name": "schema.oasf.agntcy.org/features/runtime/language",
+      "name": "schema.oasf.outshift.com/features/runtime/language",
       "version": "v0.0.0"
     }
   ],

docs/dir/hosted-agent-directory.md

@@ -179,17 +179,17 @@ available commands.
 An Agent Directory record is stored in JSON format. The record is specific
 to one entry in the Agent Directory. The structure of each AD record is
 defined by the
-[Open Agentic Schema Framework](https://schema.oasf.agntcy.org/objects/agent)
-starting at the root with an [Agent object](https://schema.oasf.agntcy.org/objects/agent).
+[OASF](/docs/oasf/open-agentic-schema-framework.md)
+starting at the root with an [Agent object](https://schema.oasf.outshift.com/objects/).
 
 To be useful, an agent record should include at least the following:
 * Name of the agent (the name MUST match the organization and repository name in the Outshift Agent Directory), 
 * Version of the agent (use semantic convention)
 * Description (something to help any viewer understand what your agent does, what is the use case it is applicable to, expected inputs and outputs, LLM used, runtime, etc)
-* Locator, per [OASF locator objects](https://schema.oasf.agntcy.org/objects/locator?extensions=)
+* Locator, per [OASF locator objects](https://schema.oasf.outshift.com/objects/locator?extensions=)
   * type(s) (source code, agent as a service, docker image, etc) matching the supported types in the OASF locator objects
   *  url (corresponding address to find the agent)
-* Skills - MUST follow the [OASF skills schema](https://schema.oasf.agntcy.org/skills?extensions=)
+* Skills - MUST follow the [OASF skills schema](https://schema.oasf.outshift.com/skills?extensions=)
 
 And it will look like this
 

docs/how-to-guides/agent-record-guide.md

@@ -15,7 +15,7 @@ Start by filling out the basic metadata of your agent:
 
 ## Define Skills
 
-The skills section outlines your agent’s capabilities. Retrieve skills definitions from the [OASF schema catalog](https://schema.oasf.agntcy.org). Each skill must include the following:
+The skills section outlines your agent’s capabilities. Retrieve skills definitions from the [OASF schema catalog](https://schema.oasf.outshift.com). Each skill must include the following:
 
 * `category_name`: The category which the skill belongs to (for example, Natural Language Processing).
 * `category_uid`: The unique identifier for the category.
@@ -39,7 +39,7 @@ You can also provide the source code:
 
 ## Specify Extensions
 
-The extensions section is critical for describing the features and operational parameters of your agent. To ensure compatibility, you must select extensions from the [OASF main features catalog](https://schema.oasf.agntcy.org/main_features?extensions). Examples of common extensions are the following:
+The extensions section is critical for describing the features and operational parameters of your agent. To ensure compatibility, you must select extensions from the [OASF main features catalog](https://schema.oasf.outshift.com/main_features?extensions). Examples of common extensions are the following:
 
 1. Runtime Framework  
     Defines the runtime environment for the agent.

docs/identity/credentials.md

@@ -2,7 +2,7 @@
 
 ## Definitions
 
-The [`AGNTCY`](https://agntcy.org/) supports various types of verifiable credentials, referred to as VCs. A verifiable credential is a specific way to express and present a set of claims made by an issuer, such as an agent definition (e.g., an [`OASF Definition`](https://schema.oasf.agntcy.org/objects/agent), or an [`A2A Agent Card`](https://github.com/google/A2A/blob/main/specification/json/a2a.json#AgentCard)), a deployment configuration, or an authorization claim that could be used during a MFA process.
+The [`AGNTCY`](https://agntcy.org/) supports various types of verifiable credentials, referred to as VCs. A verifiable credential is a specific way to express and present a set of claims made by an issuer, such as an agent definition (e.g., an [`OASF Definition`](https://schema.oasf.outshift.com/objects), or an [`A2A Agent Card`](https://github.com/google/A2A/blob/main/specification/json/a2a.json#AgentCard)), a deployment configuration, or an authorization claim that could be used during a MFA process.
 
 ### Key Verifiable Credentials (VCs)
 

docs/index.md

@@ -38,7 +38,7 @@ The initial set of IoA components and architecture is outlined below. This is a
 ![IoA Stack](assets/ioa_stack.png)
 
 1. **Agent Identity**: A system that leverages decentralized technologies to manage and verify the identities of Agents or Tools issued by any organization, ensuring secure and trustworthy interactions.
-2. **Open Agent Schema Framework (OASF)**: An OCI based extensible data model allowing to describe agents' attributes and ensuring unique identification of agents. OASF supports the description of A2A agents, MCP servers and can be extended to support other popular formats, such as Copilot agent manifests and many more. Current OASF repo can be found [here](https://github.com/agntcy/oasf), OASF schema documentation can be found [here](https://schema.oasf.agntcy.org).
+2. **Open Agent Schema Framework (OASF)**: An OCI based extensible data model allowing to describe agents' attributes and ensuring unique identification of agents. OASF supports the description of A2A agents, MCP servers and can be extended to support other popular formats, such as Copilot agent manifests and many more. Current OASF repo can be found [here](https://github.com/agntcy/oasf), OASF schema documentation can be found [here](https://schema.oasf.outshift.com).
 3. **Agent Directory**: Allows announcing and discover agents or multi-agent applications which are described using OASF. Any organization can run its directory and keep it in sync with others, forming the Internet of Agents inventory. Agent Directory supports A2A agent cards, ACP agent manifests, and MCP server descriptions among other data models.
 4. **Semantic SDK**:
     * Support various protocols: A2A, MCP, and ACP.

docs/oasf/model.proto.md

@@ -59,7 +59,7 @@ class Extension {
 | authors     | 3       | string         | Repeated | List of agent’s authors in the form of `author-name <author-email>`.                                     |
 | created_at  | 4       | string         |          | Creation timestamp of the agent in the RFC3339 format. Specs: https://www.rfc-editor.org/rfc/rfc3339.html  |
 | annotations | 5       | string, string | Map      | Additional metadata associated with this agent.                                                            |
-| skills      | 6       | string         | Repeated | List of skills that this agent is capable of performing. Specs: https://schema.oasf.agntcy.org/skills      |
+| skills      | 6       | string         | Repeated | List of skills that this agent is capable of performing. Specs: https://schema.oasf.outshift.com/skills      |
 | locators    | 7       | Locator        | Repeated | List of source locators where this agent can be found or used from.                                        |
 | extensions  | 8       | Extension      | Repeated | List of extensions that describe this agent more in depth.                                                 |
 

docs/oasf/oasf-data-model.md

@@ -29,7 +29,7 @@ message Agent {
     map<string, string> annotations = 5;
 
     // List of skills that this agent is capable of performing.
-    // Specs: https://schema.oasf.agntcy.org/skills
+    // Specs: https://schema.oasf.outshift.com/skills
     repeated string skills = 6;
 
     // List of source locators where this agent can be found or used from.

docs/oasf/oasf-server.md

@@ -4,7 +4,7 @@ The server/directory contains the Open Agents Schema Framework (OASF) Schema Ser
 The schema server is an HTTP server that provides a convenient way to browse and use the OASF schema.
 The server provides also schema validation capabilities to be used during development.
 
-You can access the OASF schema server, which is running the latest released schema, at [schema.oasf.agntcy.org](https://schema.oasf.agntcy.org).
+You can access the OASF schema server, which is running the latest released schema, at [schema.oasf.outshift.com](https://schema.oasf.outshift.com).
 
 The schema server can also be used locally.
 

docs/oasf/open-agentic-schema-framework.md

@@ -1,6 +1,6 @@
 # Open Agentic Schema Framework
 
-The [Open Agentic Schema Framework (OASF)](https://schema.oasf.agntcy.org/) is a standardized schema system for
+The [Open Agentic Schema Framework (OASF)](https://schema.oasf.outshift.com/) is a standardized schema system for
 defining and managing AI agent capabilities, interactions, and metadata. It
 provides a structured way to describe agent attributes, capabilities, and
 relationships using attribute-based taxonomies. The framework includes

docs/oasf/workflow.md

@@ -68,7 +68,7 @@ Choose a **unique** field you want to add, `uid` in the example above and popula
     3. Specific description of `uid` in the `agent` object:
         1. `uid` : `Unique Identifier/s of the reported agent."`
 3. `type`: Review OASF data_types and ensure you utilize appropriate types while defining new fields.
-    1. All the available data_types can be accessed [here](https://schema.oasf.agntcy.org/data_types).
+    1. All the available data_types can be accessed [here](https://schema.oasf.outshift.com/data_types).
     2. They are also accessible in your local instance of the oasf server (http://localhost:8000/data_types).
 4. `is_array`: This a boolean key:value pair that you must add if the field you are defining is an array.
     1. For example: `"is_array": true`
@@ -138,7 +138,7 @@ An example `locator.json` object file:
         }
         ```
 
-**Note:** If you want to create an object which would act only as a base for other objects, you must prefix the object `name` and the actual `json` filename with an `_`. The resultant object will not be visible in the [OASF Server.](https://schema.oasf.agntcy.org/objects). For example, take a look at the [entity](https://github.com/agntcy/oasf/blob/main/schema/objects/_entity.json) object.
+**Note:** If you want to create an object which would act only as a base for other objects, you must prefix the object `name` and the actual `json` filename with an `_`. The resultant object will not be visible in the [OASF Server](https://schema.oasf.outshift.com/objects). For example, take a look at the [entity](https://github.com/agntcy/oasf/blob/main/schema/objects/_entity.json) object.
 
 Sample entry in the `dictionary.json`: