top | item 32193220

The UOR-Universal Object Reference Framework

41 points| kiyanwang | 3 years ago |next.redhat.com | reply

19 comments

order
[+] rayiner|3 years ago|reply
Why am I getting CORBA PTSD reading this?
[+] ChrisMarshallNY|3 years ago|reply
Yup.

The more things change, the more they stay the same…

[+] tgv|3 years ago|reply
But with calls over the internet! I propose a new acronym: Serverless CORBa with Universal Transport over Unified Streams, aka SCORBUTUS.
[+] scrame|3 years ago|reply
Is that what that feeling in the back of my head was?
[+] vacwbcoc|3 years ago|reply
It looks like there is more info in their docs: https://universalreference.io/docs/faq/
[+] naasking|3 years ago|reply
This was illuminating:

> Universal Object Reference (UOR) provides a single format to publish, retrieve, and interact with any content. By “any content” we mean literally anything.

Then comes this:

> UOR has 4 principles that enable truly universal support for any and all content. Those are: > > 1. All content is formatted into a Directed Acyclic Graph (DAG)

So then UOR can't describe a cyclic graph? Doesn't sound like "anything" to me. It sounds like you might have to represent cyclic data using embedded runtime objects.

[+] vivegi|3 years ago|reply
For the Web, REST + HATEOAS architectural constraint is already a universal object reference framework.
[+] naasking|3 years ago|reply
I was going to say, don't we already have URLs and URIs?
[+] fulafel|3 years ago|reply
In the universal runtime picture, it seems to be drawn as a browser feature, is that right?
[+] rurban|3 years ago|reply
Security nightmares all over. There is a good reason why not all primitives or arrays or hashes are not objects, esp. over the wire.