วีดีโอ

Love, love, love!

It’s astonishing to see that so very little people see this in America.

Love it! Who did it?

Is there a digital library that collects the TDs? Like the most used sensors or more complex iot devices

Thank you for the update and the hard work. I wanted to mention that the slides currently require a W3C account login. I am unsure whether this was intentional.

I love how the W3C and the implementers and spec authors are reaching out like this to the larger web developer community. Thanks, Rachel.

I have started to read the standards but I do not know How should I start to read and understand them?

this helped me a lot in guiding me, thanks

I would love to see more quality content like this! Can we, please, have more video releases on DIDs and VC and how they might integrate with RDF and PROV?

Clown!

Es increíble como el creador de la WEB (HTML) Tim Berners-Lee apenas lo conocen y en 05/06/2024 cuenta con 60 likes, incluido el mío. Gracias, Timothy John Berners-Lee, por tremendo aporte a la humanidad y a la dispersión del conocimiento. ¡Mil gracias!

do we have already spatial anchors exchange between multiple users and devices?

Thank you so much for such a clear description!

Does he mention Interplanetary File System (IPFS) as a local caching solution?

Very cool to see well-known URIs adopted in this way! :)

This was really a lot more interesting than I thought it would be and I hope we get more videos about this as it develops. On the down side, my poor single cell brain (at least that's what it feels like when confronted with math) is now having serious issues as it try shooting of on all sorts of tangents!

Finally a good color system.

How did this go, with input on worker threads?

Nice but looks like Matter is gaining better traction?

This is all so friggin cool!!! Can’t believe how far CSS has come since the IE6 era. Once CSS 2.1 was widely adopted, CSS feature releases have just been a whirlwind. Amazing stuff!

SOLID is a solution for 20 years ago and its time has passed, W3C standards of decentralized identifiers and decentralized web nodes with confidential personal data stores is what the modern web requires.

I'm looking for accessible solutions to complex equations in Word and PDF files. This looks promising.

nearly 20 minutes ... I'm glad I said "Here's a *brief* look..."

99% of this went right over my head (self taught and an idiot) but it was really interesting and I look forward to seeing what the various coders around the world produce using these. The only part that disapointed (but only by a tiny bit) was getPredictedEvents(). I thought for one brief moment that W3C had actually solved the time travel problems! Alas not - well not yet anyway 🤣

Will the view transition api be integrated with React?

Is sRGB equivilant to Rec.709 Signals?

incredibly insightful ty!

why cant html make sense in vr? 3d css is well defined and uv mapping 2d data into 3d is a well explored field of science

Always love Miriam's talks, this one is no exception!

This is a great presentation of OKLab, thank you!

Pretty neat! I do a LOT of scene-referred HDR drawing using Krita. While I work in HDR, I usually render to SDR, in the form of Rec709 or sRGB, using the ACES tonemapper. I don't know much about actually *displaying* HDR content, though, but learning more about it is a goal I have.

Great info

What cable is better for Hdr? Hdmi or DP?

This is great, thank you so much!

Really informative, thanks for sharing

DID's claim to be truly decentralized is not quite accurate. Its methods registry needs to be managed (it should be) to insure that methods are globally unique. Without this, DIDs would not be able guaranteed unique as methods could be duplicated across multiple DID providers. The method registry is no different from a DNS name and it seems that they will used as branding with all the disadvantage that this entails when you try to guarantee persistence. DID claims to be persistent but persistence is not a really a technical issue (unless you have a really bad design (ex: URIs and brand names in DNS…). Persistence is mostly a product of social and organizational contracts. These social contracts need to be public and their policies known for them to be trusted. DID does not (yet) require social contract between DID providers. When a DID provider fails there will be a very high chance for all the DID's under that provider to disappear. Because of the method, it is unlikely that other providers with difference methods would claim that other company’s method. Because there is an explosion of DID methods, there will be a commensurate explosion of non-persistent DIDs. In many respects DIDs do not solve the good old URLs 404 problem from 30 years ago. DIDs are mostly a naming convention with the addition of a specific data model which is too complicated for its own good. The specific technical approach for storing the ID is inconsequential from a user's perspective. Blockchain, SQL, gerbils spinning wheels.... Do you care what DB amazon uses? No, you care about the services it provides. In the end, why pick a DID provider over another? Price, availability, performance, and consistency. If your DID service provider fails, you made a mistake in your DID provider selection process. Clearly not all DID will be the same which means that DIDs does not solve the persistence problem. Organizations have been using DOIs (Based on the Handle System technology) for a long time for their persistence. With DOIs there is a social contract for persistence and a guarantee that a failure of one provider will result in that provider’s DOIs (handles) to be taken up by the other DOI members. The handle system (an implementation of DO-IRPV3.0 standard which invalidated RFC 3650, 3651, and 3652) has pioneered many of DID's features but purposely remained generic in nature to maximize its ability to be used for something else. The handle system It can easily incorporate the DID data model and could easily be integrated as a DID. T The DONA Foundation operates the Global Handle Registry in collaboration with a set of global Multi-Primary-Administrators which are exclusively responsible for managing their names space. (Cryptographic validations of each namespace operation are required but the MPA who has credentials to do so). The GHR is NOT centralized. In the future, we can already predict that there will be many non-resolvable DID as the same issues that affect URIs will affect DIDs. Moving forward that it could be that DIDs will be equated with broken unreliable identifiers. A system is only as reliable as its weakest chain and DIDs are as weak as their weakest method provider. In future, like todays persistent URI, the DIDs that will continue to work reliably with be those based on the handle system identifiers such as DOIs, EIDRs, as well as other identifiers run by large corporations and government that have either social contracts for the long term. While imitation is the nicest of compliment, it took W3C 20 years to admit that URL/URIs do not cut it when it comes to PIDs. It is disappointing that W3C's internal politics prevented it to work with CNRI decades ago when they did not want to have anything to do with the Handle System as it was an non URL compliant system (Because of the intrinsic limitations of the URL RFC and URI RFCs). Unfortunately, it seems that this lack of interest in collaborating with organizations that have a proven track record of persistence for that last 20 year is still prevalent. That is a shame.

crazy to me this only has 100 views. Also how do we join these working groups.

Great video! Please make more, would love an update each year. This stuff is so cool!

"WebXR is entirely based around WebGL". does this mean you can't use WebGPU and WebXR together? Any plans to migrate WebXR from WebGL to the newer WebGPU? Real World geometry functionality so you can do physics with real world stuff is amazing. Geographic alignment is perfect for theme parks.

Cool

Don't know if the P2P aspect is being worked on yet, but one thing I wanted to suggest, as we move towards better security in the IT world, is that we need some sort of ISP level NAT 'protection' from exposing our router's public IP address. Otherwise, with a network sniffer, you can see the other people's IP in a peer to peer, but if the ISP had a P2P NAT server, only their IP would be exposed, making P2P a very safe option. The term 'P2P NAT server' is just a concept right now, but I think it could be a thing.

awesome tech! this will improve site loading!

Thank you. Very helpful.

Do you have any example repos for demo DID?

Thank you, this is very helpful!

Lesson learned: Don't keep on Flux (display temperature adjustment) during a presentation. :p Sorry for the pink hue!

This is all so cool!!!

Was informative thanks for the great content.

Thank you!!!!, i built a gaming pc with a HDR monitor, but jsut turning on the setting in settings made the screen look weird, I went in to the actual monitors settings and turned it on, now it looks great!!!

Really clear!! Thank you Ivan