Merge pull request #25 from wonsuk73/main

Fix Typo and Biblios for Core and Encoding specs
COVESA · Sep 30, 2024 · 1fff0bf · 1fff0bf
2 parents cda79e7 + c026965
commit 1fff0bf
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 12 deletions.
diff --git a/spec/VISSv3.0_Core.html b/spec/VISSv3.0_Core.html
@@ -32,12 +32,6 @@
         edDraftURI: "https://github.com/COVESA/vehicle-information-service-specification/blob/gh-pages/spec/VISSv3.0_Core.html",
         shortName: "viss3.0-core",
         localBiblio: {
-          "SemVer": {
-            title: "Semantic Versioning 2.0.0",
-            href: "https://semver.org/spec/v2.0.0.html",
-            status: "published",
-            publisher: "Tom Preston-Werner"
-          },
           "viss3-payload-encoding": {
             title: "COVESA VISS version 3.0-Payload Encoding",
             href: "https://raw.githack.com/COVESA/vehicle-information-service-specification/main/spec/VISSv3.0_PayloadEncoding.html",

diff --git a/spec/VISSv3.0_PayloadEncoding.html b/spec/VISSv3.0_PayloadEncoding.html
@@ -31,11 +31,10 @@
         edDraftURI: "https://github.com/COVESA/vehicle-information-service-specification/blob/gh-pages/spec/VISSv3.0_PayloadEncoding.html",
         shortName: "viss3.0-payload-encoding",
         localBiblio: {
-          "SemVer": {
-            title: "Semantic Versioning 2.0.0",
-            href: "https://semver.org/spec/v2.0.0.html",
-            status: "published",
-            publisher: "Tom Preston-Werner"
+          "viss3-core": {
+            title: "COVESA VISS version 3.0 - Core",
+            href: "https://raw.githack.com/COVESA/vehicle-information-service-specification/main/spec/VISSv3.0_Core.html",
+            publisher: "Ulf Bjorkengren"
           },
           "viss3-transport-examples": {
             title: "COVESA VISS version 3.0-Transport Examples",
@@ -381,7 +380,7 @@ <h2>Encoding and Decoding with Protobuf</h2>
             <h2>JSON schema based encoding</h2>
             <p>
             Several IDLs may take a JSON scheme representation of the interface description as input, e. g. OpenAPI and asyncAPI.
-            The JSON scheme representation of the VISS3.0 interface in the CORE specification can be used for such a purpose.
+            The JSON scheme representation of the VISSv3.0 interface in the CORE specification can be used for such a purpose.
             </p>
           </section>