> For the complete documentation index, see [llms.txt](https://library.xrguild.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.xrguild.org/ethical-responsibility/an-xr-ethics-framework.md). # An XR Ethics Framework For all the ways that immersive technologies can be used for good, they can be used for evil. ## Overview **Authors:** Kent Bye **Publication Date:** 21 December 2021 **Link:** **Keywords:** XR Ethical Dilemmas, Human Rights in XR, Ethical Design, Responsible Innovation, Techno-Social Impact, Political and Economic Implications, IEEE XR Ethics, Contextual Tradeoffs, Immersive Technology Risks, Ethically-Aligned Design. **Type:** Video ## Summary For all the ways that immersive technologies can be used for good, they can be used for evil. This talk will provide some conceptual frames for making sense of the landscape of XR ethical dilemmas including human rights principles, tradeoffs between contextual dimensions, and mapping relationships between techno-social, political, and economic domains. This talk will be reporting back on some of the work done by the IEEE Global Initiative on the Ethics of Extended Reality, as well as provide insights into how to integrate ethically-aligned design and responsible innovation best practices into your experiential design process. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://library.xrguild.org/ethical-responsibility/an-xr-ethics-framework.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.