Personal report by Jeremy Carroll
This summarizes the documents published by, or in an advanced state of preparation by the Semantic Web Best Practices and Deployment Working Group, and other WGs with which the SWBPD is co-operating.
Documents are listed in the following table, with more detail below (typically the document abstract).
In Semantic Web languages, such as RDF and OWL, a property is a binary relation; that is, it links two individuals or an individual and a value. How do we represent relations among more than two individuals? How do we represent properties of a relation, such as our certainty about it, severity or strength of a relation, relevance of a relation, and so on? The document presents ontology patterns for representing n-ary relations and discusses what users must consider when choosing these patterns.
This document addresses the issue of using classes as property values in OWL. While OWL Full and RDF Schema do not put any restriction on using classes as property values, OWL DL and OWL Lite do not generally allow this use. The document examines different approaches to representing this ontological pattern in OWL DL and discusses considerations that the users should keep in mind when choosing one of the approaches.
There are many "qualities", "features", or "modifiers" used to describe other concepts, e.g. size, severity, texture, rank, for which in any one ontology there is a specified collection of 'values'. This document describes two methods to represent such collections of values: as partitions of classes or as enumerations of individuals. It does not disscuss the use of datatypes to represent lists of values.
SKOS Core is a supporting RDF Vocabulary for describing concepts and concept schemes. (A 'concept scheme' is defined here as 'a description of a set of concepts, optionally including a description of relationships between those concepts'.) In general terms, the main function of SKOS Core is to support structured descriptions of conceptualisations, for the purpose of establishing common meaning within a community of people.
SKOS Core is also proposed as a standard framework for creating RDF descriptions of the more linguistically oriented types of knowledge organisation system, such as thesauri, subject heading schemes, terminologies, glossaries, classifications schemes, other controlled vocabulary types etc.
This guide is an introduction to the features of SKOS Core for readers who already have a understanding of basic RDF concepts. It is also a normative guide to the proper use of the SKOS Core vocabulary.
This document gives an overview of the SKOS Core Vocabulary. It is automatically generated from the RDF description of the SKOS Core Vocabulary. The latest version of this document can be relied upon to reflect the current state of the SKOS Core Vocabulary. This document should be read in conjunction with the latest version of the SKOS Core Guide.
This document is a quick guide to creating an RDF description of a thesaurus, and of thesaurus metadata, and publishing these on the web.
Note: this work is being driven from outside the SWBPD WG, GRDDL from the Semantic Web Coordination Group, and XHTML2 and RDF/A from the HTML WG.
This document presents GRDDL, a mechanism for encoding RDF statements in XHTML and XML to be extracted by programs such as XSLT transformations.
The Metainformation Module defines elements that allow the definition of relationships. These may relate to:
This section of the XHTML2 Working Draft is not explicitly aware of RDF, but was designed with an awareness of RDF and was intended to be RDF compatible. This compatibility is made more explicit in the next document, and we hope that the next Working Draft of XHTML2 will incorporate those ideas.
The aim of this document is to outline a syntax for layering RDF information on any XML document, via attributes.
The main focus is on XHTML as the target XML vocabulary, but the document is written with greater generality. It is believed that this will be worked into XHTML2.
The Resource Description Framework (RDF) is a language developed by the W3C for representing information about resources in the World Wide Web. Topic Maps is a standard for knowledge integration developed by the ISO. This document is the first deliverable of the RDF/Topic Maps Interoperability Task Force initiated by the W3C with the support of the ISO Topic Maps committee (ISO/IEC JTC1/SC34). It contains a survey of existing proposals for integrating RDF and Topic Maps data and is the starting point for establishing standard guidelines for RDF/Topic Maps interoperability.
This document contains a set of test cases to be used when evaluating existing and new proposals for mapping RDF data to Topic Maps and vice versa. It consists of two sections covering Topic Maps examples and RDF examples respectively. The goal of this document is to provide a complete set of test cases that illustrates every aspect of both models. A limited subset of simple test cases, intended to form the principal basis for illustrating differences between existing proposals, is selected.
The following three documents are not related to other documents.
The RDF and OWL Recommendations use the simple types from XML Schema. This document discusses three questions left unanswered by these Recommendations: What URIref should be used to refer to a user defined datatype? Which values of which XML Schema simple types are the same? How to use the problematic xsd:duration in RDF and OWL?
Metadata element sets, taxonomies, subject headings, thesauri, and ontologies are examples of vocabularies which are increasingly used in a "Semantic Web" environment. Managing vocabularies for use in Semantic Web applications means identifying, documenting, and publishing vocabulary terms in ways that facilitate their citation and re-use in a wide range of applications. This paper examines practices in the maintenance communities for representative vocabularies ranging from small and informal to large and complex. The paper formulates principles of good practice and summarizes discussion on issues for which good practice has yet to emerge.
(This version is out-of-date and should be updated shortly).
ODM will have:
Currently design is based on ontology definition languages like RDF, OWL, topic maps with "modeling" needs served by UML.
We use OWL full as the core, with mappings in/out to the others. There is also a mapping from OWL Full to UML.
Main purpose of mappings is to use UML tools to model and generate OWL, RDF, topic maps... But another purpose is to leverage existing UML models.
Less mature things include: