{"id":501,"date":"2012-01-18T22:42:20","date_gmt":"2012-01-18T22:42:20","guid":{"rendered":"http:\/\/www.spimewrangler.com\/blog\/?p=501"},"modified":"2012-01-18T22:47:11","modified_gmt":"2012-01-18T22:47:11","slug":"ar-standards-community","status":"publish","type":"post","link":"https:\/\/www.spimewrangler.com\/blog\/getting-together-for-content-and-networking\/ar-standards-community\/","title":{"rendered":"AR Standards Community"},"content":{"rendered":"<p>When we place a phone call, we don&#39;t insert a pre-fix for Blackberry phone, a different prefix for calling someone who uses an iPhone and another for Android users. A call request is placed and connected, regardless of the device and software used by the receiver&#39;s handset.&nbsp; When people publish content for the Web (aka &quot;to be viewed using a browser&quot;), they don&#39;t need to use a special platform for Internet Explorer, a special content management system or format for Opera Software users, another for Firefox users, and another for those who prefer to use Safari. And, as a result of substantial effort on the part of the mobile ecosystem, the users of mobile Web browsers can also view the same content as on a stationary device, adapted for the constraints of the mobile platform.<\/p>\n<p>With open standards, content publishers can reach the largest potential audiences and end users can choose from a wealth of content sources.<\/p>\n<p>Augmented Reality content and experiences should be available to anyone using a device meeting minimum specifications. If we do not have standards for AR, all that can and could be added to reality will remain stuck in proprietary technology silos.<\/p>\n<p>In the ideal world, where open standards triumph over closed systems, the content a publisher releases for use in an AR-enabled scenario will not need to be prepared differently for different viewing applications (software clients running on a hardware platform).<\/p>\n<p>The <a href=\"http:\/\/www.arstandards.org\">community working towards open and interoperable AR<\/a> will be <a href=\"http:\/\/www.perey.com\/ARStandards\/fifth-international-ar-standards-meeting\/\">meeting March 19-20 in Austin, Texas<\/a> to continue the coordination activities it performs on behalf of all content publishers, AR experience developers and end users.<\/p>\n<p>If you can come, and even if you are unable to meet in person with the leaders of this community, you can influence the discussion by <a href=\"http:\/\/www.perey.com\/ARStandards\/fifth-meeting-position-papers\/\">submitting a position paper according to our guidelines<\/a>. <br \/>\n\t&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When we place a phone call, we don&#39;t insert a pre-fix for Blackberry phone, a different prefix for calling someone who uses an iPhone and another for Android users. A call request is placed and connected, regardless of the device and software used by the receiver&#39;s handset.&nbsp; When people publish content for the Web (aka [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[75,6,92],"tags":[],"class_list":["post-501","post","type-post","status-publish","format-standard","hentry","category-augmented-reality","category-getting-together-for-content-and-networking","category-standards"],"_links":{"self":[{"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/posts\/501","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/comments?post=501"}],"version-history":[{"count":2,"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/posts\/501\/revisions"}],"predecessor-version":[{"id":503,"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/posts\/501\/revisions\/503"}],"wp:attachment":[{"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/media?parent=501"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/categories?post=501"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.spimewrangler.com\/blog\/wp-json\/wp\/v2\/tags?post=501"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}