add Q&A from 1.0.0 webinar

docs/community-events/20241115-releasing-1.0.0.md

@@ -3,8 +3,9 @@ title: 1.0.0 Release
 parent: Community Events
 ---
 
-{: .announcement }
-Reminder: Join us on Wednesday November 20th, 2024 at 1:30pm ET for the webinar [A Lap Around TROLIE 1.0](https://community.linuxfoundation.org/events/details/lfhq-lf-energy-presents-a-lap-around-trolie-10/)!
+{: .nb }
+Thank you to everyone who joined us for the webinar [A Lap Around TROLIE 1.0](https://community.linuxfoundation.org/events/details/lfhq-lf-energy-presents-a-lap-around-trolie-10/)!
+Please see the [recap](#recap) below, including the [Q&A](#qa).
 
 # 1.0.0 Release
 
@@ -22,3 +23,41 @@ so expect to see the spec version to change accordingly. When all is said and do
 the TROLIE 1.0 project's API specification may have a version number of 1.1.8, but
 that will be considered TROLIE 1.0. Again, we refer the reader to the [versioning
 strategy](../decision-log/media-type-versioning) for more details.
+
+# Webinar Recap
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/dk4s3tt1SEU?si=mYtzkA2sReqJTAhH" title="A Lap Around TROLIE 1.0" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+
+## Q&A
+
+### Is the Java client the underlying engine for GE's LEP product?
+
+The GE Vernova Limit Exchange Portal does make use of the [Java client](https://github.com/trolie/java-client-sdk).
+
+### Is a .NET client sdk also being considered or just create our own based on how the java sdk is done?
+
+A .NET client would be a fantastic contribution to the project, but it is not
+currently on the roadmap. If this is something you are interested in helping get
+off the ground, please contact the maintainers.
+
+### Is there a TO-to-TO ratings clearinghouse for shared facilities similar to the RC-to-RC seams process that was discussed? Local "global" ratings will need to be determined. 
+
+If a TO is within an RC footprint, then TROLIE’s expectation is for the
+Reliability Coordinator (RC) to host the Clearinghouse, such that TO-to-RC-to-TO
+will serve all the coordination needs.  Transmission Owners can obtain detailed
+limits snapshots from their RC’s Clearinghouse to obtain the ratings that were
+provided by their neighboring Transmission Owners.
+
+Some Transmission Providers/RCs may also have the underlying seasonal ratings
+from each Transmission Owner in the detailed seasonal ratings snapshot, unless
+that seasonal rating determination is made by the TOP  and contributed directly
+by them.
+
+However, if a TO is also serving RC responsibilities, as may be required of a
+vertically-integrated utility, then this same RC-to-RC process may be used to
+coordinate with that TO’s neighbors.
+
+### I would love to see more examples of what it will look like from a utility side and break down the payloads that [Ratings Providers] will be sending in to [their RC].
+
+Watch this space: [better forecast submission examples and detailed walkthrough
+· Issue #216 · trolie/spec](https://github.com/trolie/spec/issues/216).