Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-charter W3C/OGC working group #1445

Open
sgrellet opened this issue Jan 8, 2025 · 11 comments
Open

Re-charter W3C/OGC working group #1445

sgrellet opened this issue Jan 8, 2025 · 11 comments

Comments

@sgrellet
Copy link

sgrellet commented Jan 8, 2025

The initial discussion stems from SSN/SOSA work : w3c/sdw-sosa-ssn#223

As feedback from W3C and OGC on the draft charter is being discussed it seems better to discuss the comments here as non specific to SSN/SOSA

@dr-shorthair
Copy link
Collaborator

dr-shorthair commented Jan 15, 2025

W3C feedback is

  1. adjust name to Spatiotemporal Data Working Group - this WG is responsible for OWL-Time - two extensions are currently on the table
  1. add GeoDCAT to the targets or deliverables

Temporal work could also refer to the pending OGC Abstract Spec - Topic 25

@chris-little
Copy link
Contributor

@dr-shorthair Is there a consensus on spatiotemporal versus spatio-temporal? I think this is a rather minor but important point!

  1. Wikipedia seems to have only a short, older, article on the former portmanteau.
  2. Paper dictionaries seem to prefer the latter, as they view it as a neologism.
  3. The OGC API-EDR standard was sloppily split between both, and we've just done an edit to go for the hyphenated latter, as it seemed better English English, and doesn't seem to cause any problems with editting tools or search engines.

@ldesousa
Copy link

@dr-shorthair Is there a consensus on spatiotemporal versus spatio-temporal? I think this is a rather minor but important point!

  1. Wikipedia seems to have only a short, older, article on the former portmanteau.
  2. Paper dictionaries seem to prefer the latter, as they view it as a neologism.
  3. The OGC API-EDR standard was sloppily split between both, and we've just done an edit to go for the hyphenated latter, as it seemed better English English, and doesn't seem to cause any problems with editting tools or search engines.

Chris, I am not a native speaker, but I would expect my high school teacher to mark "spatiotemporal" as incorrect. High school was quite a while ago though.

@bert-github
Copy link
Contributor

I thought it was British vs American spelling. And as W3C uses American English, I chose the version without a hyphen.

But I can easily change it. If that works better with spell checkers, search engines or other software, or if people find it easier to read, that's a good enough reason.

@chris-little
Copy link
Contributor

@bert-github Is probably correct. The only other fuel to add to the fire is that the online Oxford English Dictionary quotes sources for both, covering the last 100 years or so, and the hyphens dominate, but perhaps not so much recently. I find the hypenated spelling much easier to read and type.

@TallTed
Copy link
Member

TallTed commented Jan 28, 2025

+1 for the hyphen.

@dr-shorthair
Copy link
Collaborator

I don't have strong feelings either way. They both communicate the same sense.

@rjksmith
Copy link
Member

WebVMT Update

I can confirm that WebVMT is still under active development, as detailed in the W3C Strategy Funnel issue and SDW mailing list.

I’m aiming to achieve a number of goals for WebVMT within the next charter period, including:

  1. Update the Editor’s Draft with issues identified in the OGC Testbeds and documented in the WebVMT Community Group, including negative cue times, heading and simplified interpolation.
  2. Publish a revised W3C/OGC Group Note which includes these enhancements.
  3. Register IANA media type for text/vmt to address the breaking changes to text/vtt which are already supported by HTML.
  4. Publish the HTML DataCue API proposed in WICG in collaboration with W3C Media & Entertainment IG.

Section 3.1 of the draft charter states that "existing specifications are in scope for potential maintenance” and explicitly lists WebVMT, which may be sufficient provided that this covers the four goals above.

Can someone confirm this please? Thanks

I'm concerned that the JWOC reference does not appear in the draft charter. My understanding is that this enables OGC members to participate in W3C activities as Invited Experts, which is critical to successfully achieving these four goals.

@dr-shorthair
Copy link
Collaborator

@rob-metalinkage @ldesousa @bert-github I think this ball is in your court.

@ldesousa
Copy link

ldesousa commented Jan 31, 2025

@rjksmith Those goals fall within the scope. Naturally, some of those activities do not depend solely on the SDWWG, but you can well consider it as the "home" for WebVMT development and maintenance.

As for the JWOC, I never heard of it before, and from what I can tell it existed solely as an informal construct (@rob-metalinkage correct me here please). However, the new charter states clearly in the Scope section: "Work with OGC Standard Working Groups to jointly develop, maintain and promote geospatial Web standards". By and the large, the SDWWG already works in close coordination with the GeoSemantics DWG of the OGC, and is the spirit of the charter to keep it that way.

@rjksmith
Copy link
Member

rjksmith commented Feb 1, 2025

@ldesousa Excellent. Many thanks for your confirmation and ongoing support. I can confirm that other W3C/OGC groups will certainly be involved, and I'll continue to report progress on these activites to SDW.

@ogcscotts may be able to shed more light on the details of JWOC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants