Open PersuasiveData opened 7 years ago
a. My view is that this is more-likely to be a high-level concept of mixedReality; which may range from VR to a blend and perhaps also have implications for other IoT things; in-part, depending on the device(s).
b. It's unlikely people want kids catching pokemons on freeways. therefore i was thinking of gameSafeZone or some similar concept.
Another may be to provide information about allowedActivities (which gets perhaps too complicated); or, have an array of values that have boolean responses.
Point being; people probably don't want adult virtual graffiti being left on their home doorstep, unless of course they put it there themselves. Not sure people want others trespassing to catch pokemons either.
Similarly; perhaps drones need some sorta cues to know where to go and where not to.
@PersuasiveData - I'm interested in your code; can you please format it so that it is readable? Thanks!
(Click the "Styling with Markdown is supported" link for help.)
This issue is being tagged as Stale due to inactivity.
See issue #7 for the context of the move from the main Schema.org issue tracker to this repository.
(I've updated the original post for readability of the code example.)
Hi. I am working with a company that makes 3D cameras and provides hosting/embedding services for their client’s projects. Their clients, purchase the camera, and then use the company’s SaaS solutions to provide 3D photography and scanning services for their clients. At this moment, they’ve asked me to keep their name confidential until they get some clearance; but we wanted to get this conversation going with you as soon as possible.
I’ve been with them to create structured data integrations not only for their site, but most importantly for the embedded 3D spaces their clients use to share their productions. Think YouTube—once a photographer uploads their photos to the system, they can then grab an embed URL, currently an iFrame source, to do with what they will. It’s this embed code we want to create proper schema markup that will allow us to identify my client, their customers, and their customer’s customer properly, when any of the embeds are shared throughout the Web.
The markup below is our attempt to extend the MediaObject to now include a VirtualRealityObject, just as AudioObject and VideoObject life within MediaObject. My client’s productions have their own file types, encoding types, media players, etc. All of which mimic the variety of properties shared between the sub-MediaObjects. Further, beyond my client, it seems this approach would facilitate the variety or growing properties and schemas related to the evolving world of VR and Mixed Reality media, assets, and experiences.
This is my first stab at how we’d want to look at this being integrated. I went ahead an used the old extension markup, as I am not sure how to fully communicate with you in the new extension approach. Hoping to get some directives and insights from your minds at this point!
Thanks! Aaron