Not a problem. We can leave it here if there isn’t support within the community at the time being.
I understand that these are longer term, strategic goals that may not align with other stakeholders although they could have a significant impact on where Jakarta goes from here. Clouds will evolve and my hope is that Jakarta evolves
to support the emerging technologies that will make current systems obsolete.
It is interesting that you mentioned blockchain. We are incorporating many blockchain technologies into our cloud including decentralized identity services using public blockchains that is interoperable between both public and
private blockchains as well as traditional systems. To be continued.
Charles,
I was in the expert group of JSR 321 and also did some presentations including JavaOne US or JavaOne Moscow (where especially a TPM is not even legal to use, but I did no demos ;-)
I have a hard time understanding how this relates to Jakarta EE? Are you thinking of exposing some aspects of Gen-Z via Jakarta Security, because that's pretty much the only existing spec I could think of benefiting from this kind of technology.
It does feel to be on a much different (ISO/OSI) layer than where Jakarta EE plays, therefore if there is no access to it via Jakarta EE Security, not sure if Jakarta EE was the right place for it?
A recent JCP member also told me about the idea for a general purpose Blockchain JSR. Not sure, if he goes for it, but that is also something I imagine could still make a good JSR but as a Jakarta EE spec I would not really see that kind of stuff, it is
also on a slightly different layer.