Abi ep docs#1102
Conversation
| ## Install | ||
| See the [WinML install section](https://onnxruntime.ai/docs/install/#cccwinml-installs) for WinML-related installation instructions. | ||
|
|
||
| ### Python |
There was a problem hiding this comment.
mention the URL to pypi source -
http://pypi.org/project/onnxruntime-ep-openvino/
Also refer the Nuget source URL too. @jatinwadhwa921 please provide the same
| ## Usage | ||
|
|
||
| **Python Package Installation** | ||
| To explicitly request the OpenVINO™ EP within a WinML-based application, use the V2 API: |
There was a problem hiding this comment.
mention the exact API name instead of just V2, Replacing AppendExecutionProvider_V2 with AppendExecutionProvider_OpenVINO_V2 (this is the exact WinML API) mention it explicitly
| {: .no_toc } | ||
|
|
||
| {: .note } | ||
| **Note: The built-in OpenVINO™ Execution Provider in the upstream ONNX Runtime repository is now in legacy mode.** Active development and releases have moved to the Intel-maintained fork at [intel/onnxruntime](https://github.com/intel/onnxruntime). For new projects on Windows, consider [WinML](WinML-ExecutionProvider.md), which provides automatic hardware-aware EP selection including support for Intel devices. |
There was a problem hiding this comment.
We must mention that legacy will soon reach end of development cycle & the latest winml updates will be pushed via pypi & nuget. If we state that active development is ongoing on intel fork then end users & consumers might presumme that we have the ABI EP source code hosted in Legacy EP codebase.
2 participants
Description
Motivation and Context