Next Generation RDF and SPARQL - Revision history

Marco at 19:01, 6 September 2025

2025-09-06T19:01:05Z

← Older revision		Revision as of 19:01, 6 September 2025
Line 11:		Line 11:
	<font size=-1><i>Registration Count: 109 (2025/06/10)</i></font>		<font size=-1><i>Registration Count: 109 (2025/06/10)</i></font>

	<center><iframe key="lotico" path="/lotico/reg.php?event=NextGenRDF&eurl=Next_Generation_RDF_and_SPARQL" w="500" h="230" /></center><br>		<center><!-- iframe key="lotico" path="/lotico/reg.php?event=NextGenRDF&eurl=Next_Generation_RDF_and_SPARQL" w="500" h="230" / --></center><br>

	<HR>		<HR>

Marco at 19:00, 6 September 2025

2025-09-06T19:00:07Z

← Older revision		Revision as of 19:00, 6 September 2025
Line 11:		Line 11:
	<font size=-1><i>Registration Count: 109 (2025/06/10)</i></font>		<font size=-1><i>Registration Count: 109 (2025/06/10)</i></font>

	<center><~~!--~~ iframe key="lotico" path="/lotico/reg.php?event=NextGenRDF&eurl=Next_Generation_RDF_and_SPARQL" w="500" h="230" / --></center><br>		<center><iframe key="lotico" path="/lotico/reg.php?event=NextGenRDF&eurl=Next_Generation_RDF_and_SPARQL" w="500" h="230" /></center><br>

	<HR>		<HR>

Marco at 22:02, 1 September 2025

2025-09-01T22:02:45Z

← Older revision		Revision as of 22:02, 1 September 2025
Line 17:		Line 17:


	The W3C working group is tasked with ~~devel8oping~~ the next-generation RDF and SPARQL recommendations. With significant progress already made, the latest developments will be shared directly by the group’s participants.		The W3C working group is tasked with developing the next-generation RDF and SPARQL recommendations. With significant progress already made, the latest developments will be shared directly by the group’s participants.

	The Lotico community is excited to host a presentation on the future of RDF. We'll begin by exploring the new reification scheme in RDF 1.2, which introduces triples as a new object type, alongside IRIs, blank nodes, and literals. This enhancement improves the reification mechanism, enabling "linking to links."		The Lotico community is excited to host a presentation on the future of RDF. We'll begin by exploring the new reification scheme in RDF 1.2, which introduces triples as a new object type, alongside IRIs, blank nodes, and literals. This enhancement improves the reification mechanism, enabling "linking to links."

Marco at 07:49, 18 June 2025

2025-06-18T07:49:44Z

← Older revision		Revision as of 07:49, 18 June 2025
Line 12:		Line 12:

	<center><!-- iframe key="lotico" path="/lotico/reg.php?event=NextGenRDF&eurl=Next_Generation_RDF_and_SPARQL" w="500" h="230" / --></center><br>		<center><!-- iframe key="lotico" path="/lotico/reg.php?event=NextGenRDF&eurl=Next_Generation_RDF_and_SPARQL" w="500" h="230" / --></center><br>

			<HR>
			<center><youtube>https://www.youtube.com/watch?v=RjpJlG_sGwk</youtube></center>

Marco: /* Event Recap */

2025-06-12T12:12:22Z

Event Recap

← Older revision		Revision as of 12:12, 12 June 2025
Line 67:		Line 67:
	Niklas presented on RDF 1.2's new capability to use triples as objects, explaining how this enables more sophisticated data modeling compared to traditional RDF triples. He demonstrated how triples can be used to represent abstract propositions and their relationships, showing examples from various domains including provenance, Wikidata, and academic degrees. The presentation covered both the technical syntax and semantics of this feature, including the concept of reifiers and how they can be used to add context and qualifications to simple facts. Niklas emphasized that while this feature builds on existing RDF concepts, it provides a more flexible way to handle complex relationships and varying levels of granularity in data modeling.		Niklas presented on RDF 1.2's new capability to use triples as objects, explaining how this enables more sophisticated data modeling compared to traditional RDF triples. He demonstrated how triples can be used to represent abstract propositions and their relationships, showing examples from various domains including provenance, Wikidata, and academic degrees. The presentation covered both the technical syntax and semantics of this feature, including the concept of reifiers and how they can be used to add context and qualifications to simple facts. Niklas emphasized that while this feature builds on existing RDF concepts, it provides a more flexible way to handle complex relationships and varying levels of granularity in data modeling.
	</P>		</P>
	RDF Reifiers for Complex Relationships<br>		<br>RDF Reifiers for Complex Relationships<br>
	<br>		<P>
	Niklas presented on the use of reifiers in RDF to handle complex relationships, demonstrating how they can be used to add granular details to simple relationships without requiring complete remodelling of data. He explained that while n-ary relationships would be a better approach in some cases, the existing simple model must be maintained due to production constraints, and showed how reifiers can be used with OWL for advanced reasoning. The discussion concluded with a comparison to named graphs, clarifying that while they serve different use cases and are complementary designs, reifiers and named graphs address different aspects of data management.		Niklas presented on the use of reifiers in RDF to handle complex relationships, demonstrating how they can be used to add granular details to simple relationships without requiring complete remodelling of data. He explained that while n-ary relationships would be a better approach in some cases, the existing simple model must be maintained due to production constraints, and showed how reifiers can be used with OWL for advanced reasoning. The discussion concluded with a comparison to named graphs, clarifying that while they serve different use cases and are complementary designs, reifiers and named graphs address different aspects of data management.

			</P>
	<br>RDF Version Transition Planning<br>		<br>RDF Version Transition Planning<br>

	The working group has been focusing on the transition from RDF 1.1 to RDF 1.2, including new syntax features like triple terms and text direction for literals. They have introduced a versioning mechanism to help smooth the adoption of these changes across the web, allowing for content negotiation and future-proofing. The group has also developed a basic encoding for triple terms and confirmed that existing RDF toolkits can handle the new versioning parameters without issues.		The working group has been focusing on the transition from RDF 1.1 to RDF 1.2, including new syntax features like triple terms and text direction for literals. They have introduced a versioning mechanism to help smooth the adoption of these changes across the web, allowing for content negotiation and future-proofing. The group has also developed a basic encoding for triple terms and confirmed that existing RDF toolkits can handle the new versioning parameters without issues.

	<br>RDF 1.2 Features and Applications<br>		<br>RDF 1.2 Features and Applications
			<P>
			This part of the meeting focused on RDF 1.2 and its implications, with presentations by Niklas and Andy highlighting new features like reification and nested triples. Participants discussed practical applications, compatibility issues, and potential use cases for these features. Questions were raised about the significance of text direction, the relationship between RDF 1.2 and SHACL, and the potential for using RDF Star to achieve functionality similar to named graphs. The group also touched on the need for clarity in the specifications and the importance of robustness in handling different scripts and display directions.</P>

	This part of the meeting focused on RDF 1.2 and ~~its implications~~, ~~with presentations by Niklas~~ and Andy ~~highlighting new features like reification and nested triples~~. ~~Participants discussed practical applications, compatibility issues,~~ and ~~potential use cases for these features. Questions were raised about the significance of text direction~~, ~~the relationship between~~ RDF 1.2 and ~~SHACL~~, and ~~the potential for using~~ RDF ~~Star to achieve functionality similar to named graphs~~. ~~The group also touched on~~ the ~~need~~ for ~~clarity in the specifications~~ and ~~the importance~~ of ~~robustness in handling different scripts~~ and ~~display directions~~.		<br>RDF 1.2 and SPARQL Updates
			<P>
			This part of the meeting focused on RDF 1.2 and SPARQL compatibility, implementation timelines, and ongoing development. Andy explained that RDF 1.2 and SPARQL are largely compatible, with RDF 1.2 including updates like RDF JSON data type formalization and clarifications on initial text direction. Michael inquired about implementation timelines, and Andy suggested that core specifications could be ready in a few months, with major vendors like Jenna and Oxigraph planning to support RDF 1.2 soon. Alex asked about the W3C process for recommendation status, and Andy clarified that two implementations of each feature are required, not two complete implementations. The conversation ended with a reminder about upcoming sessions and events related to RDF and SPARQL development.</P>

	~~<br>RDF 1.2 and SPARQL Updates<br>~~		<br>RDF Triples and SPARQL Syntax
			<P>
	This part of the meeting focused on RDF 1.2 and SPARQL compatibility, implementation timelines, and ongoing development. Andy explained that RDF 1.2 and SPARQL are largely compatible, with RDF 1.2 including updates like RDF JSON data type formalization and clarifications on initial text direction. Michael inquired about implementation timelines, and Andy suggested that core specifications could be ready in a few months, with major vendors like Jenna and Oxigraph planning to support RDF 1.2 soon. Alex asked about the W3C process for recommendation status, and Andy clarified that two implementations of each feature are required, not two complete implementations. The conversation ended with a reminder about upcoming sessions and events related to RDF and SPARQL development.		This part of the meeting focused on discussing the use of triples in RDF and SPARQL, with Niklas explaining that triples cannot be used as subjects to avoid abstract propositions being treated as concrete entities, following community group reports on the "Seminal Error." Andy and Niklas clarified that while RDF 1.2 and SPARQL 1.2 syntax is partially supported in Jena 1.1.5, there are no compatibility issues when using TDB 2 databases, though older versions of Jena might produce incorrect results. Marco concluded the session, thanking the participants and noting that slides and recordings would be shared, with plans for a follow-up session the following week.</P>

	<br>RDF Triples and SPARQL Syntax<br>

	This part of the meeting focused on discussing the use of triples in RDF and SPARQL, with Niklas explaining that triples cannot be used as subjects to avoid abstract propositions being treated as concrete entities, following community group reports on the "Seminal Error." Andy and Niklas clarified that while RDF 1.2 and SPARQL 1.2 syntax is partially supported in Jena 1.1.5, there are no compatibility issues when using TDB 2 databases, though older versions of Jena might produce incorrect results. Marco concluded the session, thanking the participants and noting that slides and recordings would be shared, with plans for a follow-up session the following week.

Marco: /* Event Recap */

2025-06-12T12:11:03Z

Event Recap

← Older revision		Revision as of 12:11, 12 June 2025
Line 59:		Line 59:

	Next-Generation RDF and SPARQL<br>		Next-Generation RDF and SPARQL<br>
	<br>		<P>
	The meeting began with Marco Neumann introducing the Lotico session on next-generation RDF and SPARQL, highlighting the evolution of RDF over 25 years and its current maturity in empowering developers. He mentioned the involvement of various teams and initiatives, including the W3C, and set the context for the presentation by referencing past efforts and ongoing developments. The meeting had more than 100 registered participants and Marco introduced Nicholas Lindström and Andy Seaborne, who are active participants in the W3C Working Groups, as speakers for the session. The session was structured to include presentations by Nicholas and Andy, followed by a Q&A session, and concluded with an open chat.		The meeting began with Marco Neumann introducing the Lotico session on next-generation RDF and SPARQL, highlighting the evolution of RDF over 25 years and its current maturity in empowering developers. He mentioned the involvement of various teams and initiatives, including the W3C, and set the context for the presentation by referencing past efforts and ongoing developments. The meeting had more than 100 registered participants and Marco introduced Nicholas Lindström and Andy Seaborne, who are active participants in the W3C Working Groups, as speakers for the session. The session was structured to include presentations by Nicholas and Andy, followed by a Q&A session, and concluded with an open chat.
			</P>
	<br>		<br>
	RDF 1.2 Triple Object Capabilities<br>		RDF 1.2 Triple Object Capabilities<br>
	<br>		<P>
	Niklas presented on RDF 1.2's new capability to use triples as objects, explaining how this enables more sophisticated data modeling compared to traditional RDF triples. He demonstrated how triples can be used to represent abstract propositions and their relationships, showing examples from various domains including provenance, Wikidata, and academic degrees. The presentation covered both the technical syntax and semantics of this feature, including the concept of reifiers and how they can be used to add context and qualifications to simple facts. Niklas emphasized that while this feature builds on existing RDF concepts, it provides a more flexible way to handle complex relationships and varying levels of granularity in data modeling.		Niklas presented on RDF 1.2's new capability to use triples as objects, explaining how this enables more sophisticated data modeling compared to traditional RDF triples. He demonstrated how triples can be used to represent abstract propositions and their relationships, showing examples from various domains including provenance, Wikidata, and academic degrees. The presentation covered both the technical syntax and semantics of this feature, including the concept of reifiers and how they can be used to add context and qualifications to simple facts. Niklas emphasized that while this feature builds on existing RDF concepts, it provides a more flexible way to handle complex relationships and varying levels of granularity in data modeling.
	<br>		</P>
	RDF Reifiers for Complex Relationships<br>		RDF Reifiers for Complex Relationships<br>
	<br>		<br>

Marco: /* Event Recap */

2025-06-12T12:10:32Z

Event Recap

← Older revision		Revision as of 12:10, 12 June 2025
Line 57:		Line 57:
	The Lotico meeting focused on next-generation RDF and SPARQL developments, with presentations by Nicholas Lindstrom and Andy Seaborne covering new features like reifiers, triple terms, and text direction in RDF 1.2. The discussion explored practical applications, compatibility considerations, and implementation timelines for these new capabilities, with participants addressing questions about specifications, tool support, and W3C processes. The session concluded with clarifications about triples as objects and SPARQL compatibility, while noting that slides and recordings would be shared and a follow-up meeting was scheduled in the following weeks.		The Lotico meeting focused on next-generation RDF and SPARQL developments, with presentations by Nicholas Lindstrom and Andy Seaborne covering new features like reifiers, triple terms, and text direction in RDF 1.2. The discussion explored practical applications, compatibility considerations, and implementation timelines for these new capabilities, with participants addressing questions about specifications, tool support, and W3C processes. The session concluded with clarifications about triples as objects and SPARQL compatibility, while noting that slides and recordings would be shared and a follow-up meeting was scheduled in the following weeks.

	~~Summary~~

	Next-Generation RDF and SPARQL<br>		Next-Generation RDF and SPARQL<br>

Marco: /* Event Recap */

2025-06-12T12:10:06Z

Event Recap

← Older revision		Revision as of 12:10, 12 June 2025
Line 52:		Line 52:
	=== Event Recap ===		=== Event Recap ===

	Next Generation RDF and SPARQL 1.2 - Tuesday Jun 10, 14:02-17:13 <i>Generated by a Zoom AI Companion Assistant with some manual edits</i>		Next Generation RDF and SPARQL 1.2 - Tuesday Jun 10, 14:02-17:13<br>
			<i>Generated by a Zoom AI Companion Assistant with some manual edits</i>

	The Lotico meeting focused on next-generation RDF and SPARQL developments, with presentations by Nicholas Lindstrom and Andy Seaborne covering new features like reifiers, triple terms, and text direction in RDF 1.2. The discussion explored practical applications, compatibility considerations, and implementation timelines for these new capabilities, with participants addressing questions about specifications, tool support, and W3C processes. The session concluded with clarifications about triples as objects and SPARQL compatibility, while noting that slides and recordings would be shared and a follow-up meeting was scheduled in the following weeks.		The Lotico meeting focused on next-generation RDF and SPARQL developments, with presentations by Nicholas Lindstrom and Andy Seaborne covering new features like reifiers, triple terms, and text direction in RDF 1.2. The discussion explored practical applications, compatibility considerations, and implementation timelines for these new capabilities, with participants addressing questions about specifications, tool support, and W3C processes. The session concluded with clarifications about triples as objects and SPARQL compatibility, while noting that slides and recordings would be shared and a follow-up meeting was scheduled in the following weeks.

Marco: /* Event Recap */

2025-06-12T12:09:36Z

Event Recap

← Older revision		Revision as of 12:09, 12 June 2025
Line 52:		Line 52:
	=== Event Recap ===		=== Event Recap ===

	Next Generation RDF and SPARQL 1.2 -Tuesday Jun 10, 14:02-17:13 <i>Generated by a Zoom AI Assistant</i>		Next Generation RDF and SPARQL 1.2 - Tuesday Jun 10, 14:02-17:13 <i>Generated by a Zoom AI Companion Assistant with some manual edits</i>

	The Lotico meeting focused on next-generation RDF and SPARQL developments, with presentations by Nicholas Lindstrom and Andy ~~Seabourne~~ covering new features like reifiers, triple terms, and text direction in RDF 1.2. The discussion explored practical applications, compatibility considerations, and implementation timelines for these new capabilities, with participants addressing questions about specifications, tool support, and W3C processes. The session concluded with clarifications about triples as objects and SPARQL compatibility, while noting that slides and recordings would be shared and a follow-up meeting was scheduled in the following weeks.		The Lotico meeting focused on next-generation RDF and SPARQL developments, with presentations by Nicholas Lindstrom and Andy Seaborne covering new features like reifiers, triple terms, and text direction in RDF 1.2. The discussion explored practical applications, compatibility considerations, and implementation timelines for these new capabilities, with participants addressing questions about specifications, tool support, and W3C processes. The session concluded with clarifications about triples as objects and SPARQL compatibility, while noting that slides and recordings would be shared and a follow-up meeting was scheduled in the following weeks.

	Summary		Summary

Marco at 12:06, 12 June 2025

2025-06-12T12:06:56Z

← Older revision		Revision as of 12:06, 12 June 2025
Line 52:		Line 52:
	=== Event Recap ===		=== Event Recap ===

	Next Generation RDF and SPARQL 1.2 -Tuesday Jun 10, 14:02-17:13		Next Generation RDF and SPARQL 1.2 -Tuesday Jun 10, 14:02-17:13 <i>Generated by a Zoom AI Assistant</i>

	The Lotico meeting focused on next-generation RDF and SPARQL developments, with presentations by Nicholas Lindstrom and Andy Seabourne covering new features like reifiers, triple terms, and text direction in RDF 1.2. The discussion explored practical applications, compatibility considerations, and implementation timelines for these new capabilities, with participants addressing questions about specifications, tool support, and W3C processes. The session concluded with clarifications about triples as objects and SPARQL compatibility, while noting that slides and recordings would be shared and a follow-up meeting was scheduled in the following weeks.		The Lotico meeting focused on next-generation RDF and SPARQL developments, with presentations by Nicholas Lindstrom and Andy Seabourne covering new features like reifiers, triple terms, and text direction in RDF 1.2. The discussion explored practical applications, compatibility considerations, and implementation timelines for these new capabilities, with participants addressing questions about specifications, tool support, and W3C processes. The session concluded with clarifications about triples as objects and SPARQL compatibility, while noting that slides and recordings would be shared and a follow-up meeting was scheduled in the following weeks.