add blockquote stuff

julsraemy · Feb 16, 2024 · ec37ac1 · ec37ac1
1 parent 7686cb8
commit ec37ac1
Show file tree

Hide file tree

Showing 6 changed files with 100 additions and 16 deletions.
diff --git a/_site/assets/stylesheets/style.css b/_site/assets/stylesheets/style.css
@@ -242,6 +242,44 @@ pre > code::first-line {
     background-color: yellow; /* Temporary: For visual inspection */
 }
 
+blockquote {
+    margin: 20px 0;
+    padding: 20px;
+    position: relative;
+    font-family: Georgia, serif;
+    font-size: 0.9em;
+    line-height: 1.5;
+    font-style: italic;
+    background-color: #f9f9f9;
+    border-left: 8px solid #333; /* Change color to match your theme */
+    box-shadow: 2px 2px 15px rgba(0, 0, 0, 0.1); /* subtle shadow */
+}
+
+blockquote::before,
+blockquote::after {
+    font-family: Arial, sans-serif;
+    line-height: 0;
+    position: absolute;
+    color: #007bff; /* Match vertical line color */
+}
+
+blockquote cite {
+    display: block;
+    margin-top: 10px;
+    font-style: normal;
+    text-align: right;
+    font-size: 14px;
+}
+
+@media (max-width: 600px) {
+    blockquote {
+        padding: 15px;
+        margin: 15px 0;
+    }
+}
+
+
+
 table {
     width: 100%; /* Make the table stretch to the full container width */
     border-collapse: collapse; /* Collapse borders between table cells */

diff --git a/_site/feed.json b/_site/feed.json
diff --git a/_site/feed.xml b/_site/feed.xml
diff --git a/_site/loud.html b/_site/loud.html
@@ -67,6 +67,10 @@ <h1>Linked Open Usable Data (LOUD)</h1>
 <h2>JavaScript Object Notation for Linked Data (JSON-LD)</h2>
 <p><a href="https://json-ld.org/" target="_blank" rel="noopener noreferrer">JSON-LD</a> is a modern web standard designed to simplify the encoding of linked data using the widely known JSON format. As a compact and easy-to-manage data format, JSON-LD enhances the ability to share structured data across disparate systems on the Web, while embedding rich semantic capabilities. It achieves this by allowing data to be serialised in a way that is compatible with traditional JSON, yet interpretable by RDF-based semantic processing tools.</p>
 <p>At its core, JSON-LD introduces a context (<code>@context</code>) that maps terms in a JSON document to Internationalised Resource Identifiers (IRIs) used in RDF vocabularies. This mapping allows JSON documents to be interpreted as RDF graphs, facilitating the integration of structured data into the Semantic Web without requiring developers to depart from familiar JSON syntax. The design of JSON-LD aims to bridge the gap between the ease of use of JSON and the rich data connectivity and interoperability offered by RDF. The development of JSON-LD was motivated by the need to make linked data more accessible to Web developers and to encourage wider adoption of Semantic Web technologies. By embedding semantic annotations directly into JSON, JSON-LD enables developers to contribute to the linked data cloud with a minimal learning curve, accelerating the growth of a semantically rich, interconnected web of data.</p>
+<p>Per the <a href="https://www.w3.org/TR/json-ld11/" target="_blank" rel="noopener noreferrer">JSON-LD 1.1. specification</a>:</p>
+<blockquote>
+<p>JSON-LD is a concrete RDF syntax as described in <a href="https://www.w3.org/TR/rdf11-concepts/" target="_blank" rel="noopener noreferrer">RDF11-CONCEPTS</a>. Hence, a JSON-LD document is both an RDF document and a JSON document and correspondingly represents an instance of an RDF data model. However, JSON-LD also extends the RDF data model to optionally allow JSON-LD to serialize generalized RDF Datasets.</p>
+</blockquote>
 <p>The strategic adoption of JSON-LD as a means to reconcile the simplicity of JSON with the descriptive power of RDF has sparked an insightful debate about its practical implications and its classification as a polyglot format. A <a href="https://tess.oconnor.cx/2023/09/polyglots-and-interoperability" target="_blank" rel="noopener noreferrer">blog post by Tess O’Connor</a> outlines several challenges that emerge from this approach, including issues related to dual data models, algorithmic complexity, and the potential brittleness and performance impacts of JSON-LD’s <code>@context</code> mechanism. To address these challenges, a strategic focus on simplicity and clarity is advocated. Adopting a straightforward JSON format that doesn’t require knowledge of RDF can simplify interactions and improve the appeal and usability of the data. In addition, creating canonical mappings from JSON to RDF addresses the needs of RDF users while maintaining the accessibility of the base format. In addition, the adoption of stable sets of <code>@context</code> is critical for consistent data exchange.</p>
 <p>However, this polyglot characterisation of JSON-LD has been met with counter-arguments, <a href="https://github.com/w3ctag/design-principles/issues/239#issuecomment-1762316158" target="_blank" rel="noopener noreferrer">such as those from
 Pierre-Antoine Champin</a>, that offer a different perspective. Critics argue that JSON-LD should not be considered a polyglot format in the strictest sense because it operates on a “JSON then JSON-LD” basis rather than an “either/or” scenario. In this view, any JSON-LD processor first interprets the document as JSON before applying the JSON-LD layer, similar to how other JSON formats, such as GeoJSON, encode specific types of information beyond the basic JSON structures. This process does not make these formats polyglots, but rather extensions of JSON that provide mappings to more complex data models, thus emphasising JSON-LD’s role in simplifying the transition to semantically enriched data on the web.</p>

diff --git a/assets/stylesheets/style.css b/assets/stylesheets/style.css
@@ -242,6 +242,44 @@ pre > code::first-line {
     background-color: yellow; /* Temporary: For visual inspection */
 }
 
+blockquote {
+    margin: 20px 0;
+    padding: 20px;
+    position: relative;
+    font-family: Georgia, serif;
+    font-size: 0.9em;
+    line-height: 1.5;
+    font-style: italic;
+    background-color: #f9f9f9;
+    border-left: 8px solid #333; /* Change color to match your theme */
+    box-shadow: 2px 2px 15px rgba(0, 0, 0, 0.1); /* subtle shadow */
+}
+
+blockquote::before,
+blockquote::after {
+    font-family: Arial, sans-serif;
+    line-height: 0;
+    position: absolute;
+    color: #007bff; /* Match vertical line color */
+}
+
+blockquote cite {
+    display: block;
+    margin-top: 10px;
+    font-style: normal;
+    text-align: right;
+    font-size: 14px;
+}
+
+@media (max-width: 600px) {
+    blockquote {
+        padding: 15px;
+        margin: 15px 0;
+    }
+}
+
+
+
 table {
     width: 100%; /* Make the table stretch to the full container width */
     border-collapse: collapse; /* Collapse borders between table cells */

diff --git a/src/loud.md b/src/loud.md
@@ -25,6 +25,10 @@ Linked Open Data (LOD) has been pivotal in fostering a web of openly connected d
 
 At its core, JSON-LD introduces a context (`@context`) that maps terms in a JSON document to Internationalised Resource Identifiers (IRIs) used in RDF vocabularies. This mapping allows JSON documents to be interpreted as RDF graphs, facilitating the integration of structured data into the Semantic Web without requiring developers to depart from familiar JSON syntax. The design of JSON-LD aims to bridge the gap between the ease of use of JSON and the rich data connectivity and interoperability offered by RDF. The development of JSON-LD was motivated by the need to make linked data more accessible to Web developers and to encourage wider adoption of Semantic Web technologies. By embedding semantic annotations directly into JSON, JSON-LD enables developers to contribute to the linked data cloud with a minimal learning curve, accelerating the growth of a semantically rich, interconnected web of data.
 
+Per the [JSON-LD 1.1. specification](https://www.w3.org/TR/json-ld11/): 
+
+> JSON-LD is a concrete RDF syntax as described in [RDF11-CONCEPTS](https://www.w3.org/TR/rdf11-concepts/). Hence, a JSON-LD document is both an RDF document and a JSON document and correspondingly represents an instance of an RDF data model. However, JSON-LD also extends the RDF data model to optionally allow JSON-LD to serialize generalized RDF Datasets.
+
 The strategic adoption of JSON-LD as a means to reconcile the simplicity of JSON with the descriptive power of RDF has sparked an insightful debate about its practical implications and its classification as a polyglot format. A [blog post by Tess O'Connor](https://tess.oconnor.cx/2023/09/polyglots-and-interoperability) outlines several challenges that emerge from this approach, including issues related to dual data models, algorithmic complexity, and the potential brittleness and performance impacts of JSON-LD's `@context` mechanism. To address these challenges, a strategic focus on simplicity and clarity is advocated. Adopting a straightforward JSON format that doesn't require knowledge of RDF can simplify interactions and improve the appeal and usability of the data. In addition, creating canonical mappings from JSON to RDF addresses the needs of RDF users while maintaining the accessibility of the base format. In addition, the adoption of stable sets of `@context` is critical for consistent data exchange.
 
 However, this polyglot characterisation of JSON-LD has been met with counter-arguments, [such as those from