"Thingy.v1_0_0.xml" wouldn't be its own Redfish server; this would describe an OEM extension you have in your Redfish implementation.
Most implementations server their OEM schemas on-chip, meaning they implement "/redfish/v1/Schemas/<SCHEMA-FILE>" on their service to provide the file to users. So, you would need to support the URI "/redfish/v1/Schemas/Thingy.v1_0_0.xml" and provide the file contents to the requester.
However, this shouldn't be confused with how to add the support in your service to provide the functionality described by "Thingy.v1_0_0.xml". Ultimately that would require code modifications to your service to support the extensions you're describing.
Oh I see the use of this project now, your own custom schema development. We may need that to create a Telemetry service. Thanks for that perspective! I'm getting there. Still hoping to get help from Gunner Mills too but he needs a security check for this project. I really appreciate you keepin me goin!
I have the Profile-Simulator running and that seems to be a good starting point for firing redfishtool and curl calls at something workin. Better than the emulator! Although I do like the emulator web interface better.
So somebody needs to write the O'Reilly Redfish book. Anybody start it yet? The cover would probably be another picture of a "redfish" like all the other fishing type Redfish books lol