Update id lines to new link

- removed `/schemas` from line 3 in all schema files

2791object.json

 {
     "$schema": "http://json-schema.org/draft-07/schema#",
-    "$id": "https://w3id.org/2791/schemas/2791object.json",
+    "$id": "https://w3id.org/2791/2791object.json",
     "type": "object",
     "title": "Base type for all IEEE-2791 Objects",
     "description": "All IEEE-2791 object types must adhear to this type in order to be compliant with IEEE-2791 standard",

description_domain.json

 {
     "$schema": "http://json-schema.org/draft-07/schema#",
-    "$id": "https://w3id.org/2791/schemas/description_domain.json",
+    "$id": "https://w3id.org/2791/description_domain.json",
     "type": "object",
     "title": "Description Domain",
     "description": "Structured field for description of external references, the pipeline steps, and the relationship of I/O objects.",

error_domain.json

 {
     "$schema": "http://json-schema.org/draft-07/schema#",
-    "$id": "https://w3id.org/2791/schemas/error_domain.json",
+    "$id": "https://w3id.org/2791/error_domain.json",
     "type": "object",
     "title": "Error Domain",
     "description": "Fields in the Error Domain are open-ended and not restricted nor defined by the IEEE-2791 standard. It is RECOMMENDED that the keys directly under empirical_error and algorithmic_error use a full URI. Resolving the URI SHOULD give a JSON Schema or textual definition of the field. Other keys are not allowed error_domain",

execution_domain.json

 {
     "$schema": "http://json-schema.org/draft-07/schema#",
-    "$id": "https://w3id.org/2791/schemas/execution_domain.json",
+    "$id": "https://w3id.org/2791/execution_domain.json",
     "type": "object",
     "title": "Execution Domain",
     "description": "The fields required for execution of the IEEE-2791 Object are herein encapsulated together in order to clearly separate information needed for deployment, software configuration, and running applications in a dependent environment",

io_domain.json

 {
     "$schema": "http://json-schema.org/draft-07/schema#",
-    "$id": "https://w3id.org/2791/schemas/io_domain.json",
+    "$id": "https://w3id.org/2791/io_domain.json",
     "type": "object",
     "title": "Input and Output Domain",
     "description": "The list of global input and output files created by the computational workflow, excluding the intermediate files. Custom to every specific IEEE-2791 Object implementation, these fields are pointers to objects that can reside in the system performing the computation or any other accessible system.",

parametric_domain.json

 {
     "$schema": "http://json-schema.org/draft-07/schema#",
-    "$id": "https://w3id.org/schemas/parametric_domain",
+    "$id": "https://w3id.org/parametric_domain",
     "type": "array",
     "title": "Parametric Domain",
     "description": "This represents the list of NON-default parameters customizing the computational flow which can affect the output of the calculations. These fields can be custom to each kind of analysis and are tied to a particular pipeline implementation",

provenance_domain.json

 {
     "$schema": "http://json-schema.org/draft-07/schema#",
-    "$id": "https://w3id.org/2791/schemas/provenance_domain.json",
+    "$id": "https://w3id.org/2791/provenance_domain.json",
     "type": "object",
     "title": "Provenance Domain",
     "description": "Structured field for tracking data through transformations, including contributors, reviewers, and versioning.",

usability_domain.json

 {
     "$schema": "http://json-schema.org/draft-07/schema#",
-    "$id": "https://w3id.org/2791/schemas/usability_domain.json",
+    "$id": "https://w3id.org/2791/usability_domain.json",
     "type": "array",
     "title": "Usability Domain",
     "description": "Author-defined usability domain of the IEEE-2791 Object. This field is to aid in search-ability and provide a specific description of the function of the object. It is recommended that a novel use of the IEEE-2791 Object could result in the creation of a new entry with a new usability domain",