Re: [webvmt] Status Update

Yep

Done using the BuildingBlocks we will ensure such components can be integrated with other specifications using a common mechanism.

BBs do many things - the ones that matter here are:


  1.
 link the schema to the conceptual model (using an ontology versions of the CM)
  2.
 provide transparency around the dependencies
  3.
Provide examples and validation tools for each component
  4.
Provide links to your normative schemas and other resources in a standardised way (every spec is different 🙁 )

So its not an either/or - its "let me help you realise this goal - heres some tools ready to go..."


And a draft we can evolve to match your current spec: https://opengeospatial.github.io/geopose-bblocks/bblock


I will run tutorial and editing sessions to get this up and running if its not 4am...




Rob Atkinson
Senior Research Engineer  | Open Geospatial Consortium (OGC)
Mobile: +61 419 202973
ratkinson@ogc.org<mailto:ratkinson@ogc.org> | ogc.org<http://ogc.org/> | @opengeospatial


[https://ci3.googleusercontent.com/meips/ADKq_NYvdzG5CnR-DX7WeJyPCnJuhbJ_G7lH1yVbaql72titKCiG-t4HQ92DiCCRM2jU42bDT20Ge7sBVIodm8VpmVBlrnTKCg=s0-d-e1-ft#https://portal.ogc.org/files/?artifact_id=99287]



________________________________
From: Christine Perey
Sent: Wednesday, May 14, 2025 9:23 PM
To: Rob Atkinson
Cc: Rob Smith; public-sdw-wg@w3.org; steve@opensiteplan.org
Subject: Re: [webvmt] Status Update

Hi Rob,

Regrets for not responding to your message earlier due to this coming into my inbox on a day I was traveling.

I believe that what you propose as the BBs is what the SWG is now calling the "GeoPose Components.”  See these slides<https://docs.google.com/presentation/d/1e28blobnrG9zYl_8VyhjyWHs2ZqiW2z5MS94dxHMBSU/edit?slide=id.p1#slide=id.p1> and these slides.<https://docs.google.com/presentation/d/1YLFjEXiKAGo4_o4EymYXlsTnkf9VjTkSk6QL3eRTOlY/edit?slide=id.p1#slide=id.p1>

As you will see on our GeoPose 1.x roadmap<https://geopose.org/CallForContributors.html> (and seek volunteers to contribute to) we are also separating the JSON encoding<https://github.com/opengeospatial/geopose-json-encoding> from the CM specification<https://github.com/opengeospatial/GeoPose-cm>.

Best regards,

Christine Perey
Spime Wrangler

cperey@perey.com
Swiss Mobile +41 79 436 6869

On Apr 28, 2025, at 11:00 AM, Rob Atkinson <ratkinson@ogc.org> wrote:

Hi

I'd like to move the GeoPose building blocks to a dedicated repository managed by GeoPose SWG, where you can document and add examples etc, and add any reccommended profiles for WebVMT etc,

Happy to help with this process, I'll start by getting them updated with the latest versions if required


  *
They currently point to https://schemas.opengis.net/geopose/1.0/schemata/GeoPose.Advanced.Schema.json


  *
If this is not correct then  please fix your schemas - these should be deprecated and a reference to where they are now, or update the schemas in this location or something

Note one rationale for OGC building blocks is that its currently almost impossible to find where authoritative schemas are across different generations of OGC standards due to different publishing processes over time -  by having a central knowledge graph referencing them in a common way we can mitigate this - but each SWG needs to take some responsibility to make sure its outputs are correctly registered.

Let me know if I can help further. Always willing to run training on this.  There is now a tutorial, and will be creating videos to help this year as well.




Rob Atkinson
Senior Research Engineer  | Open Geospatial Consortium (OGC)
Mobile: +61 419 202973
ratkinson@ogc.org<mailto:ratkinson@ogc.org> | ogc.org<http://ogc.org/> | @opengeospatial


[https://outlook.office.com/mail/inbox/id/AAMkADNhZWRmOGUxLTRkYTQtNDgxMi05NGI1LTAwMDM5Y2ZmZDk0MgBGAAAAAAB0BUVIbF1rSZNBzH0OpI3FBwDkWvdAfbYmRZRLVkMRlzcuAAAAAAEMAADkWvdAfbYmRZRLVkMRlzcuAAL5AVlOAAA%3D?nativeVersion=1.2025.328.300]

________________________________
From: Christine Perey <cperey@perey.com>
Sent: Monday, April 28, 2025 4:38 PM
To: Rob Smith <rob.smith@awayteam.co.uk>
Cc: Rob Atkinson <ratkinson@ogc.org>; public-sdw-wg@w3.org <public-sdw-wg@w3.org>
Subject: Re: [webvmt] Status Update

Hi Rob S.

Many thanks for these pointers and suggestions.

@Rob A

Any questions?

100% agreement that posting future GeoPose discussion issues directly to the SWG mailing list at geopose.swg@lists.ogc.org<mailto:geopose.swg@lists.ogc.org> will get the best visibility.

Best regards,

Christine Perey
Spime Wrangler

cperey@perey.com
Swiss Mobile +41 79 436 6869

On Apr 27, 2025, at 6:03 PM, Rob Smith <rob.smith@awayteam.co.uk> wrote:

Rob,

Thanks for your message about GeoPose.

1. I notice that the OGC Building Block wrappers refer to the draft GeoPose spec. I recommend that you update these to reference the OGC GeoPose Standard document [1] instead.

2. WebVMT is a current work item in scope for SDW - as previously agreed in the rechartering discussion [2]. SDW published a W3C Group Note [3] (OGC 23-027) in September 2023. Development is ongoing in collaboration with several OGC SWGs and W3C WGs including GeoPose, Moving Features and WICG DataCue [4], though these disparate topics are drawn together in SDW.

3. On the subject of ‘alignments’, a new heading attribute was developed and prototyped in Testbed-19 [5] which is aligned with GeoPose. This is designed to integrate with HTML and includes features such as heading and missing data which are beyond the current scope of GeoPose 1.0. WebVMT heading data were published in the T19 Hillyfields Bubble repo [6] under an open licence and this feature was developed further in Testbed-20.

4. I recommend posting future GeoPose discussion issues directly to the SWG mailing list at geopose.swg@lists.ogc.org<mailto:geopose.swg@lists.ogc.org> for best visibility. Thanks.

I’d welcome the opportunity to present recent WebVMT progress and future plans to help ensure that the Group is kept up to date. Please let me know when the next SDW Plenary meeting is scheduled, and I look forward to hearing from you soon.

Rob Smith

Away Team
www.awayteam.co.uk<http://www.awayteam.co.uk/>

[1] https://docs.ogc.org/is/21-056r11/21-056r11.html

[2] https://github.com/w3c/sdw/issues/1445#issuecomment-2626827076

[3] https://www.w3.org/TR/webvmt/

[4] https://github.com/WICG/datacue

[5] https://webvmt.org/demos/testbed#testbed-19

[6] https://github.com/HillyfieldsBubble/Releases/


On 24 Apr 2025, at 8:02 am, Rob Atkinson <ratkinson@ogc.org> wrote:

Hi Rob

Note we have "wrapped" GeoPose schemas here

https://opengeospatial.github.io/bblocks/register/bblock/ogc.geo.geopose.basic.quaternion

https://opengeospatial.github.io/bblocks/register/bblock/ogc.geo.geopose.advanced

https://opengeospatial.github.io/bblocks/register/bblock/ogc.geo.geopose.basic.ypr


And mapped them to a notional (but not yet extant "geopose ontology" - or URIs)

When considering "alignments" it would be of interest to have this done via such an ontology - and the ontology and alignments published by the GeoPose SWG via the SDW.

(sorry for my ignorance or forgetfulness - is WebVMT currently a work item under an existing OGC SWG? )

Rob Atkinson
Senior Research Engineer  | Open Geospatial Consortium (OGC)
Mobile: +61 419 202973
ratkinson@ogc.org<mailto:ratkinson@ogc.org> | ogc.org<http://ogc.org/> | @opengeospatial


[https://outlook.office.com/mail/inbox/id/AAMkADNhZWRmOGUxLTRkYTQtNDgxMi05NGI1LTAwMDM5Y2ZmZDk0MgBGAAAAAAB0BUVIbF1rSZNBzH0OpI3FBwDkWvdAfbYmRZRLVkMRlzcuAAAAAAEMAADkWvdAfbYmRZRLVkMRlzcuAAL5AVlOAAA%3D?nativeVersion=1.2025.328.300]

________________________________

From: Rob Smith <rob.smith@awayteam.co.uk<mailto:rob.smith@awayteam.co.uk>>
Sent: Thursday, April 10, 2025 3:45 AM
To: public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org> <public-sdw-wg@w3.org<mailto:public-sdw-wg@w3.org>>
Subject: [webvmt] Status Update

1. Progress Made
     i. Continued development of prototype polyfill for WICG DataCue API [1] to support synchronisation of video with timed metadata in web browsers.
    ii. Proposed change to expose HTML TextTrackCue constructor at MEIG meeting [2] on 4 March 2025.
    iii. Discussed details of proposed change to expose HTML TextTrackCue constructor at WICG DataCue meetings on 11 March 2025 [3] and 20 March 2025 [4].
    iv. Published explainer for proposed change to expose HTML TextTrackCue constructor [5] that enables custom cues for timed metadata in Javascript, including WICG DataCue API [1].
    v. Chaired session on Synchronising Sensors With Geotagged Video [6] at W3C Breakouts Day on 26 March 2025 to identify missing web requirements for geotagged video use cases with sensors from community feedback.
    vi. Updated Javascript playback engine on WebVMT.org<http://webvmt.org/> website [7] with prototype features developed in OGC Testbeds including negative cue times, simplified interpolation and heading.
    vii. Continued participation in OGC Testbed-20 GIMI [8] to ensure that proposed design for GIMI video timed metadata is aligned with existing formats.

2. Next Steps
    i. Create short video summary of OGC Testbed-20 GIMI maritime and aerial use case results for OGC YouTube channel [9].
    ii. Continue participation in OGC Testbed-20 GIMI [8] to ensure that proposed design for GIMI video timed metadata is aligned with existing formats.
    iii. Continue alignment discussions with OGC GeoPose SWG [10].
    iv. Continue community outreach and identify more activities to promote progress towards the standardisation track.

[1] https://wicg.github.io/datacue/#datacue-interface

[2] https://www.w3.org/2025/03/04-me-minutes.html#56c2

[3] https://www.w3.org/2025/03/11-me-minutes.html

[4] https://www.w3.org/2025/03/20-me-minutes.html

[5] https://github.com/WICG/datacue/blob/main/text-track-cue-constructor.md

[6] https://www.w3.org/2025/03/breakouts-day-2025/#b-89d32797-5c4d-4bab-a9c0-0eca1ed1a114

[7] https://webvmt.org/demos

[8] https://portal.ogc.org/files/108074#GIMI

[9] https://www.youtube.com/user/ogcvideo

[10] https://www.ogc.org/projects/groups/geoposeswg