Technical Committee: oasis augmented Reality in Information Products (arip) tc chairs
Download 49.62 Kb.
|
- Navigate this page:
- 1.1References (non-normative)
- Heading Text. Acknowledgments
- Some Appendix Text. Subsidiary Appendix Section
|
Augmented Reality for Information Products Guidelines and Best Practices Version 1.0 
Working Draft 01 03 November 2016
Rhonda Truitt (Rhonda.truitt@huawei.com), Huawei Farhad Patel (Farhad.Patel@huawei.com), Huawei
Sally Martir (sally.martir@huawei.com), Huawei Additional artifacts: This document is one component of a Work Product that also includes: Other documents or XML schemas: (list full titles or file names, with hyperlinks if available) Related work: This document is related to: related documents (list full titles, with hyperlinks if available) Abstract: This document will provide technical communicators with guidelines and best practices for developing Augmented Reality Information Products following lessons learned from successful ARIP projects. Status: This Working Draft (WD) has been produced by one or more TC Members; it has not yet been voted on by the TC or approved as a Committee Note Draft. The OASIS document Approval Process begins officially with a TC vote to approve a WD as a Committee Note or Committee Note Draft. A TC may approve a Working Draft, revise it, and re-approve it any number of times. URI patterns: Initial publication URI: http://docs.oasis-open.org/arip/arip-gabs/v1.0/cn01/arip-gabs-v1.0-cn01.docx Permanent “Latest version” URI: http://docs.oasis-open.org/arip/arip-gabs/v1.0/arip-gabs-v1.0.docx (Managed by OASIS TC Administration; please don’t modify.) Copyright © OASIS Open 2016. All Rights Reserved. All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents1.1References (non-normative) 5 1.2OASIS 6 1.2.1ARIP Committee 6 1.3Document Purpose 6 1.4Document History 7 1.5AR Description 7 1.6Benefits 7 1.7Limitations 8 OverviewAugmented Reality (AR) is a technology that allows us to overlay computer-generated content onto a user's view of the real world. This technology transforms the way we communicate and deliver work instructions, in that, we are now writing for a medium that is much more interactive and situational than anything before. This technology enables users to see their way through a task getting instructions at the exact point in time they need them. Creating content for AR requires new tools and a new way of thinking when planning and producing technical documentation. To address the needs we have as technical communicators, the Augmented Reality in Information Products (ARIP) committee created this set of guidelines to use. 1.1References (non-normative)NOTE (remove this note and following examples before publication): The proper format for citation of technical work produced by an OASIS TC (whether Standards Track or Non-Standards Track) is: Recommended approach: Set up [Reference] label elements as "Bookmarks", then use hyperlinks to them within the document. (Here’s how: Insert hyperlink ->Place in this document -> scroll down to Bookmarks, select appropriate one.) Use the "Ref" paragraph style to format references.
For example: [OpenDoc-1.2] Open Document Format for Office Applications (OpenDocument) Version 1.2. Edited by Patrick Durusau and Michael Brauer. 19 January 2011. OASIS Committee Specification Draft 07. http://docs.oasis-open.org/office/v1.2/csd07/OpenDocument-v1.2-csd07.html. Latest version: http://docs.oasis-open.org/office/v1.2/OpenDocument-v1.2.html. Reference sources: For references to IETF RFCs, use the approved citation formats at:
For references to W3C Recommendations, use the approved citation formats at: http://docs.oasis-open.org/templates/w3c-recommendations-list/w3c-recommendations-list.html. 1.2OASISThe founders of the ARIP committee searched for a standards organization that was globally accepted, robust, and allowed them to not only develop and influence the standards that affect technical communicators but that would also fast-track the approved standards through the International Standards Organization (ISO) and other standards bodies. The Organization for the Advancement of Structured Information Standards (OASIS) was founded in 1993. OASIS is a nonprofit consortium that is American National Standards Institute (ANSI)-accredited, has worldwide credibility, and is home to more than 70 technical committees. 1.2.1ARIP CommitteeThe ARIP committee is comprised of practitioners and academics in the field of technical communication representing companies and educational institutions from around the world. The founders of the committee are from Huawei Technologies, as follows: Rhonda Truitt, rhonda.truitt@huawei.com, Chair Farhad Patel, farhad.patel@huawei.com, Chair Sally Martir, sally.martir@huawei.com, Secretary 1.3Document PurposeThis document provides a set of guidelines for technical communicators to use when developing work instructions for AR projects. The guidelines cover the following aspects of an AR project: Understanding the different types of AR experiences Analyzing needs Selecting a use case Planning the project Determining resources needed for the project Determining the device(s) to use that will display the AR experience Considering software selection Understanding dependencies and gathering requirements Designing the AR experience Developing content Incorporating media into the AR experience Reviewing the AR experience Testing and validating the AR experience Storing and delivering the AR project Measuring quality These guidelines are the first step toward developing AR standards for technical communicators. As we learn more, we will update this document periodically until the guidelines are formalized as an OASIS committee specification. 1.4Document History
1.5AR DescriptionAR is a technology that superimposes computer-generated text and images on a user's view of the real world, thus providing a composite view. The main differences between AR and Virtual Reality (VR) are listed below.
1.6BenefitsAR is transforming the way people see and learn from their surroundings. In particular, work instructions (how-to information) embedded in AR experiences offer the following benefits: Instructions are part of the experience and no longer a separate entity. Augmented instructions are particularly useful for workers who are on the move or who need to have their hands free to do the work. Workers make fewer mistakes because they don’t have to take their eyes off the work at hand to refer to an external document. Workers can train on large equipment right in the comfort of their workspace. This saves on travel costs and the need for external trainers. Augmented instructions update as the user’s view changes. Contextual awareness-sensory modality. 1.7LimitationsViewing space for instructions is limited in an AR experience and you want the instructions to supplement the experience, not overtake it. For this reason, any type of documentation that isn’t a direct how-to for the task at hand is best left out of an AR experience and documented in a more traditional way. HeadingText. AcknowledgmentsThe following individuals have participated in the creation of this specification and are gratefully acknowledged: Participants: [Participant Name, Affiliation | Individual Member] [Participant Name, Affiliation | Individual Member] Some AppendixText. Subsidiary Appendix SectionText. Sub-subsidiary Appendix Sectiontext.
Directory: committees -> download.php download.php -> Emergency Interoperability Consortium Membership Meeting download.php -> Technical Communicators, Get ready: Here comes Augmented Reality! Rhonda Truitt download.php -> Oasis set tc download.php -> Iepd analyze Requirements Use Cases for edxl situation reporting messages Draft Version 4 download.php -> Technical Committee: oasis transformational Government Framework tc chair download.php -> Ibops protocol Version 0 Working Draft 2 9 March 2015 Technical Committee download.php -> Reliability of Messages Sent as Responses over an Underlying Request-response Protocol download.php -> Service Component Architecture sca-j common Annotations and apis Specification Version 1 Committee Draft 03 – Rev1 + Issue 127 download.php -> Scenario Two – Hurricane Warning download.php -> Technical Committee: oasis augmented Reality in Information Products (arip) tc chairs Download 49.62 Kb. Share with your friends:
|