100 likes | 251 Vues
This workshop, led by Dave Beckett, focuses on the importance of metadata interoperability within the framework of the Semantic Web. Key discussions revolve around the role of URIs, RDF, and XML in defining elements and terms for metadata standards. Beckett emphasizes the need for stability and persistence in URIs, detailing W3C's commitments and policies to ensure reliable namespace identification. The session aims to encourage collaboration among standards initiatives, fostering a mix of terminology and cross-application usability to advance metadata interoperability.
E N D
CORES Metadata Interoperability Workshop Dave Beckett SWAD-Europe
Dave Beckett - Background • Metadata - DCMI • Semantic Web - RDF Core • Web Developer • W3C Advisory Committee Rep.
W3C and Elements / Terms • W3C is not a registry (defer to IETF) • Terms are in specifications • Semantic web languages - URIs • URIs not necessarily for retrieval • Working with IETF on URI updates
Our standard has "elements" • Few W3C RECs are languages • Some have “elements” called: • RDF: Properties, Classes • XML: Infoitems, Facets, Particles (XSD) • For those: Yes
Identified in a citable way • “In principle, we would be willing to identify our elements in a more generalized form shared by other standards as well.” • Yes - part of the W3C mission
Identify elements with URIs • Yes (RDF, OWL do this) • But XSD uses XML Qnames • Working on the latter • Something may be behind the URI(after resolution, retrieval)
URI stability, persistence, … • Yes. • Guaranteed by W3C host institutions - Persistence Policy • /TR/ document publication policy • URIs for W3C namespaces policy(2001)
Application Layer • Mostly left to users • Applications of RDF: • Ontology Web Language (OWL) • CC/PP • WAI Content Guidelines • Applications of XML Schemas: • Few
W3C Semantic Web Activity • Welcomes this initiative • Encourage use of others terms • Want to mix and match • RDF bootstraping this with DCES • Ontology Web Language (OWL)
URI Considerations • URI schemes very expensive to deploy. • URNs getting cheaper - discovery of resolution services by DDDS • HTTP URLs very cheap • URIs do not require being online