A large variety of schema languages exist, defined inside or outside of W3C; to name a few: RDF-Schema, OWL, SHACL, ShEx, XML-Schema, JSON-Schema... Each of these languages have been favored by different categories of users, who in turn ignore, neglect, sometimes even despise the other languages, deemed "too complicated", "less powerful" or simply "not fit for purpose".
It might be tempting to consider that any schema language is worth any other, and that the "best" one is a matter of technological preferences. We argue on the contrary that these languages differ in their core purpose, and should be seen as complementary rather than competitors. More precisely:
ontology languages such as RDF-Schema and OWL focus on the conceptual modelling of the domain,
shape languages such as SHACL and ShEx focus on the logical modelling of the data,
structural schema languages such as XML-Schema and JSON-Schema focus of the physical modelling of exchange formats.
Sticking to one schema language to cover all these aspects is therefore suboptimal. Creating bridges between their user communities, to allow cross-fertilization and combined use, is a promising approach.
But it is also challenging, because it creates the need to maintain consistency across schemas at different levels. We will present different tools and methods that have been proposed to deal with this problem, and discuss the standardization opportunities in this area.
Session goal
We will discuss the complementarity of various schema languages, and which tools are available (or missing...) to make them work together.
Additional session chairs (Optional)
No response
IRC channel (Optional)
you-say-schemata-i-say-schemas
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
Session description
A large variety of schema languages exist, defined inside or outside of W3C; to name a few: RDF-Schema, OWL, SHACL, ShEx, XML-Schema, JSON-Schema... Each of these languages have been favored by different categories of users, who in turn ignore, neglect, sometimes even despise the other languages, deemed "too complicated", "less powerful" or simply "not fit for purpose".
It might be tempting to consider that any schema language is worth any other, and that the "best" one is a matter of technological preferences. We argue on the contrary that these languages differ in their core purpose, and should be seen as complementary rather than competitors. More precisely:
ontology languages such as RDF-Schema and OWL focus on the conceptual modelling of the domain,
shape languages such as SHACL and ShEx focus on the logical modelling of the data,
structural schema languages such as XML-Schema and JSON-Schema focus of the physical modelling of exchange formats.
Sticking to one schema language to cover all these aspects is therefore suboptimal. Creating bridges between their user communities, to allow cross-fertilization and combined use, is a promising approach.
But it is also challenging, because it creates the need to maintain consistency across schemas at different levels. We will present different tools and methods that have been proposed to deal with this problem, and discuss the standardization opportunities in this area.
Session goal
We will discuss the complementarity of various schema languages, and which tools are available (or missing...) to make them work together.
Additional session chairs (Optional)
No response
IRC channel (Optional)
you-say-schemata-i-say-schemas
Who can attend
Anyone may attend (Default)
Session duration
60 minutes (Default)
Other sessions where we should avoid scheduling conflicts (Optional)
No response
Estimated number of in-person attendees
Don't know (Default)
Instructions for meeting planners (Optional)
No response
Agenda, minutes, slides, etc. (Optional)