Julie Winchester

I believe we've hit a similar error to this in our somewhat-modified Hyrax application (currently running on 2.9.0) using many different work types with many different parent-child relationships between works....

Riffing on the above snippet to add the other 2 transforms at the annotation level, keeping just a translate transform at the target level. ``` { "id": "https://example.org/iiif/3d/anno1", "type": "Annotation",...

As was requested during the Basel working meeting on 10/26/2023, adding a note to say that the scale transform as indicated here is using degrees (rather than radians) for reasons...

Though part of this is also stated by @julsraemy above, I wanted to detail some general consensus items from the Basel conference working meeting on October 26, 2023: * Transforms...

In addition to the three standard transforms `TranslateTransform`, `RotateTransform`, and `ScaleTransform`, I think it would make sense to provide an additional convenience transform `TranslateToOriginTransform` (or some other name similar to...

I'll add a second personal opinion to echo @tomcrane that degrees are more human friendly, trivial for computers to convert to radians, and will help ensure that the JSON manifest...

Maybe this issue should be closed as completed?

For spotlights in three.js, the angle is indeed the half-angle of the spotlight cone. Here is an example demonstrating a spotlight angle of 90 degrees: https://codepen.io/JellyfishJail/pen/vYPwNvx (copied and only slightly...

I don't think I'm a huge fan of option 2. My preference here would be for us to avoid inferred properties, especially where it's difficult for an end user to...

This was discussed during the TSG meeting on April 3rd. There was some general support for going for an initial "readable"/"simple" solution of RotateTransform specifying an Euler transform with a...