OMI glTF Working Group Meeting 2022-10-27 #113
Replies: 4 comments
-
OMI_linkLink extension should be added to a node with the OMI_collider extension. Implementation details of how the link behaves (navigate on click or navigate on collide) is up to the client. Metadata for the link can be gathered through a WebFinger-like API where you pass the URL and receive metadata like thumbnail, title, and description. {
"nodes": [
{
"name": "Link",
"extensions": {
"OMI_link": {
"uri": "https://omigroup.org/worlds/meetup"
},
"OMI_collider": {
...
}
}
}
]
} |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
OMI_colliderAdded some new comments on referring to colliders via indices vs placing definitions on nodes: |
Beta Was this translation helpful? Give feedback.
-
three-omiDiscussed some implementation details for this PR, implementing KHR_audio omigroup/three-omi#10 |
Beta Was this translation helpful? Give feedback.
-
This meeting will be on 10/27/2022 at 10:30 PM (UTC) / 2:30 PM (PST) in the OMI Discord within the #omi-weekly-meeting channel. During the meeting, we will be using the #omi-gltf-extensions channel to manage a speaker queue, post links, and for any sidebar discussions.
To be notified of this meeting and others, subscribe to the OMI Meetings and Events Calendar or add yourself to the @omi-gltf-subgroup role in the #roles channel of the OMI Discord.
Last Week's Agenda for reference:
To propose another item for the agenda, comment below (preferably before the meeting).
Beta Was this translation helpful? Give feedback.
All reactions