Breakout
Group 1
Longevity of URIs in a changing environment.
Changes of vocabularies/datasets while keeping the same namespace can cause applications to fail.
How do we (and particularly industry!) know which vocabularies and technologies that have strong community backing?
Longevity of URIs in a Changing Environment Newly developed vocabularies believed to reach external uptake should be hosted by W3C, or possibly PURL.org. For existing vocabularies; log and publish statistics on read access so that it can be determined which existing vocabularies are heavily used, in order to learn how signi cant this potential problem is.
Possibly consider how BitTorrent anchor links work; could their approach to DNS-less resource resolution work also for Semantic Web data?
Changes to Vocabularies
Never change a published (i.e., available via a publicly resolvable URI) vocabulary or dataset - only add new URI:s with new versioning info.
Further work needed on Ontology Evolution and logging, particularly regarding presenting change deltas in an accessible user-friendly or at least developer-friendly way. Related to the above: the use of the deprecation warning and versioning annotations in OWL needs to be increased. Could a system be developed to generate reports from a codebase, detailing which datasets/vocabularies/libraries that the code depends upon? Emphasize the use of and development of indices like LOV and LodStats, possibly also for other types of artefacts than just vocabularies.
Could a social networking-based community portal be of use? Currently the semantic web research community exists across a great deal of sites, keeping it all in one place and combining this with a user-maintained directory of quality components and technologies might be bene cial.