Technical Committee: oasis augmented Reality in Information Products (arip) tc chairs



Download 47.66 Kb.
Date23.04.2018
Size47.66 Kb.

Augmented Reality for Information Products Guidelines and Best Practices Version 1.0

Working Draft 01

03 November 2016

Technical Committee:

OASIS Augmented Reality in Information Products (ARIP) TC

Chairs:

Rhonda Truitt (Rhonda.truitt@huawei.com), Huawei

Farhad Patel (Farhad.Patel@huawei.com), Huawei

Editor:

Sally Martir (sally.martir@huawei.com), Huawei



Additional artifacts:

This document is one component of a Work Product that also includes:



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 Contents


1.1References (non-normative) 5

1.2Section Level 2 5

1.2.1Section Level 3 5

1.3Section Level 2 5

1.4Content 7

1.5Technology 7

1.6User 7

1.7Who is the ideal end-user? 8

1.8Artifact gathering (user manuals, product info, etc) & conversion for Augmented Reality 10

1.9Minimizing Content 10

1.10Using colors 10

1.11Metadata 10

1.12Superimposing graphics/Digital Overlays 10

1.13Corrections/ Next 10

1.14Show vs. Tell 10

1.15Embedded content 10

1.16Links 10

1.17Single-sourcing 10

1.18Structured Mark Up 11

1.19Languages 11

1.20Plan B 11



















Introduction


Type introductory text here.

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.

[Citation Label] Work Product title (italicized). Edited by Albert Alston, Bob Ballston, and Calvin Carlson. Approval date (DD Month YYYY). OASIS Stage Identifier and Revision Number (e.g., OASIS Committee Specification Draft 01). Principal URI (version-specific URI, e.g., with stage component: somespec-v1.0-csd01.html). Latest version: (latest version URI, without stage identifiers).

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:
http://docs.oasis-open.org/templates/ietf-rfc-list/ietf-rfc-list.html.

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.2Section Level 2

1.2.1Section Level 3

1.3Section Level 2



Analysis


Before you create content for delivery in an AR platform, you should perform an analysis of the requirements for content structure and formats, the available technology, the intended audience, the cost/benefit of delivering content on the AR platform, and any potential risks.

1.4Content


To perform a content analysis, you must first identify the set of available information (an inventory of current content), and identify any gaps of required information.

An outline of the expected task sequences and any necessary supporting conceptual or reference content is essential in determining the scope of content that must be created or updated for the particular project you intend to deliver to AR.

Cognitive mapping may be useful to help visualize the relationships between each of the content components and determine the required semantic connections that need to be established.

AR content should embrace minimalism, providing just the right information at the right time.


1.5Technology


When analyzing the available technology, determine if the primary use is intended for one of the following categories:

  • geospatial system—informational overlays based on current GPS location

  • 2-D AR system—detection of a QR code or other symbol to activate display of content

  • 3-D AR system—overlay of 3D parts, components or other content based on tracking capabilities

Once the appropriate category is determined for the content, determine the capabilities of your delivery platform or application. Does it have access to GPS information? Does it have access to visual recognition and a camera? Does it have access to 3-D CAD source models, 3-D point clouds or other tracking information?

1.6User


The single-most important analysis for AR content is the user analysis. Answer the following questions about your intended audience:

  • What do they need to know or do?

  • What are their real goals?

  • Where will they use this information?

  • How do we present information to help them meet their goals?

To create content that meets the needs of your audience, you might need to know their education and experience levels, reading ability, job role, typical tasks, goals and expectations, environment and safety considerations.

1.7Who is the ideal end-user?


Once you identify the potential audiences of your content and AR platform, consider performing a deeper analysis of the ideal end-user to clearly identify the target content formats (text, animation, video, interactivity, or other), and their devices that need to support the consumption of the AR information.


Content Development


Text.

1.8Artifact gathering (user manuals, product info, etc) & conversion for Augmented Reality


Text.

1.9Minimizing Content


Text.

1.10Using colors


Text.

1.11Metadata


Text.

1.12Superimposing graphics/Digital Overlays


Text.

1.13Corrections/ Next


Text.

1.14Show vs. Tell


Text.

1.15Embedded content


Text.

1.16Links


Text.

1.17Single-sourcing


Text.

1.18Structured Mark Up


Text.

1.19Languages


Text.

1.20Plan B


Text.





  1. Acknowledgments


The following individuals have participated in the creation of this specification and are gratefully acknowledged:

Participants:

Scott Hudson, Boeing

[Participant Name, Affiliation | Individual Member]


  1. Some Appendix


Text.
  1. Subsidiary Appendix Section


Text.
  1. Sub-subsidiary Appendix Section


text.
  1. Revision History


Revision

Date

Editor

Changes Made

[Rev number]

[Rev Date]

[Modified By]

[Summary of Changes]




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 -> This is intended as a Non-Standards Track Work Product. [Type the document title]

Download 47.66 Kb.

Share with your friends:




The database is protected by copyright ©ininet.org 2020
send message

    Main page