This blog post will address how Semantic Treehouse supported the needs of a data sharing community in creating a new standard. Among the dedicated users of Semantic Treehouse is the SETU foundation, the organization for data standardization of the flexible staffing industry in the Netherlands. Recently, SETU developed the Planning and Scheduling standard, enabling seamless data exchange of planning information between staffing suppliers back-office software, planning tools, and interconnecting planning tools.
For this Planning and Schedulling standard, there was a desire to repurpose HR Open specification whenever feasible. This involved creating multiple message models by carefully selecting elements from the HR Open Model in JSON Schema and incorporating SETU specific additions and restrictions. Furthermore, SETU's goal was also to create schemas in both JSON and XML formats, along with Open API specifications for seamless implementation and validation. The following text highlights how Semantic Treehouse supported the SETU foundation in reaching their goals.
The SETU foundation has been using the Semantic Treehouse to publish, maintain, and create all of their standards. In addition, SETU uses the Semantic Treehouse for its community portal to maintain content and practical insights from working group meetings. This collaborative space also serves as a hub for providing additional information, such as attendees or the agenda. It allows SETU and their working groups to consolidate everything in a single location.
As mentioned, SETU wanted to reuse the HR Open Specification wherever necessary. For their own SETU-specific concepts and restrictions, they have created their own information model (RDF and SHACL). The Semantic Treehouse provided SETU with the capability to publish these specifications and use them as a starting point within the FIT wizard, enabling them to create their distinct SETU-specific message models.
This empowerment allowed SETU to redesign the structures of HR Open Specifications and change individual elements where needed. This involves introducing new SETU-specific sub-elements, but also customizing the initial elements, for example, by changing the cardinality or the description. In essence, the Semantic Treehouse granted SETU the freedom to shape messages precisely as they envisioned.
Another goal of SETU was to create schemas in both JSON and XML formats, along with Open API specifications for seamless implementation and validation. The Semantic Treehouse assisted SETU by automatically generating schemas for the standards in both XML and JSON formats. Furthermore, the output of the Open API generator within the Semantic Treehouse served as a starting point for SETU to easily create their own API Specification for their standards.
Would you like to know more about the SETU Planning and Schedulling standard, please refer to the SETU documentation page, or feel free to contact us. We are here to help!