fix: Add additionalProperties annotations to match benchmark schema (#42)

Author: mahdanoura

resources/schemas/hypermedia.yaml

@@ -124,6 +124,11 @@ classes:
     description: >-
       A link can be viewed as a statement of the form "link context has a relation type resource at link target", 
       where the optional target attributes may further describe the resource.
+    annotations:
+      jsonschema_config:
+        tag: jsonschema_config
+        value:
+          additionalProperties: true
     attributes:
       href:
         description: Target IRI of a link or submission target of a form.
@@ -169,86 +174,43 @@ classes:
   Form:
     class_uri: hctl:Form
     description: >-
-      A form can be viewed as a statement of "To perform an operation type operation on form context, make a 
-      request method request to submission target" where the optional form fields may further describe the required 
-      request. In Thing Descriptions, the form context is the surrounding Object, such as Properties, Actions, and 
-      Events or the Thing itself for meta-interactions.
-    comments:
-      - >-
-        If no response name-value pair is provided, it MUST be assumed that the content type of the response 
-        is equal to the content type assigned to the Form instance
-      - >-
-        If the content type of the expected response differs from the content type of the form, the Form instance 
-        MUST include a name-value pair with the name response
-    attributes:
+      A form hypermedia control that describes how an operation can be performed.
+    annotations:
+      jsonschema_config:
+        tag: jsonschema_config
+        value:
+          additionalProperties: true
+    slots:
+      - op
+      - href
+      - contentType
+      - contentCoding
+      - subprotocol
+      - security
+      - scopes
+      - response
+      - additionalResponses
+    slot_usage:
+      op:
+        range: string
+        pattern: ^(readproperty|writeproperty|observeproperty|unobserveproperty|invokeaction|queryaction|cancelaction|subscribeevent|unsubscribeevent|readallproperties|writeallproperties|readmultipleproperties|writemultipleproperties|observeallproperties|unobserveallproperties|queryallactions|subscribeallevents|unsubscribeallevents)$
+        multivalued: true
       href:
-        description: Target IRI of a link or submission target of a form.
-        slot_uri: hctl:hasTarget
-        range: uri
         required: true
+        range: uri
       contentType:
-        description: >-
-          Assign a content type based on a media type (e.g., text/plain) and potential parameters 
-          (e.g., charset=utf-8) for the media type [RFC2046].
-        slot_uri: hctl:forContentType
         range: string
       contentCoding:
-        description: >-
-          Content coding values indicate an encoding transformation that has been or can be applied to a 
-          representation. Content codings are primarily used to allow a representation to be compressed or 
-          otherwise usefully transformed without losing the identity of its underlying media type and without 
-          loss of information. Examples of content coding include "gzip", "deflate", etc.
-        slot_uri: hctl:forContentCoding
         range: string
+      subprotocol:
+        range: string
+        pattern: ^(longpoll|websub|sse)$
       security:
-        description: >-
-          Set of security definition names, chosen from those defined in securityDefinitions. These must all be 
-          satisfied for access to resources.
         range: string
         multivalued: true
       scopes:
-        description: >-
-          Set of authorization scope identifiers provided as an array. These are provided in tokens returned by 
-          an authorization server and associated with forms in order to identify what resources a client may 
-          access and how. The values associated with a form SHOULD be chosen from those defined in an 
-          OAuth2SecurityScheme active on that form.
         range: string
         multivalued: true
-      response:
-        description: >-
-          This optional term can be used if, e.g., the output communication metadata differ from input metadata 
-          (e.g., output contentType differ from the input contentType). The response name contains metadata that 
-          is only valid for the primary response messages.
-        slot_uri: hctl:returns
-        range: ExpectedResponse
-      additionalResponses:
-        description: >-
-          This optional term can be used if additional expected responses are possible, e.g. for error reporting.
-          Each additional response needs to be distinguished from others in some way (for example, by specifying
-          a protocol-specific error code), and may also have its own data schema.
-        slot_uri: hctl:additionalReturns
-        range: AdditionalExpectedResponse
-        multivalued: true
-      subprotocol:
-        description: >-
-          Indicates the exact mechanism by which an interaction will be accomplished for a given protocol when 
-          there are multiple options. For example, for HTTP and Events, it indicates which of several available 
-          mechanisms should be used for asynchronous notifications such as long polling, WebSub, Server-Sent Events (also known as EventSource).
-        slot_uri: hctl:forSubProtocol
-        range: string
-        comments:
-          - e.g., longpoll, websub, or sse
-      op:
-        description: >-
-          Indicates the semantic intention of performing the operation(s) described by the form. For example, 
-          the Property interaction allows get and set operations. The protocol binding may contain a form for 
-          the get operation and a different form for the set operation. The op attribute indicates which form 
-          is for which and allows the client to select the correct form for the operation required.
-        slot_uri: hctl:hasOperationType
-        exactly_one_of:
-          - range: OperationType
-          - range: OperationType
-            multivalued: true
 
   ExpectedResponse:
     class_uri: hctl:ExpectedResponse