Open Data Patterns for Organisations
Open Org is an informal group wanting to create and collect good practice for organistaions wanting to create Open and Linked Data.
This wiki will be used to collect patterns and tools, and also to improve those patterns if they are found to be flawed. The default data will be assumed to be RDF, but variations are fine if that's sensible.
Open Data Patterns for Open Orgs
These pages should describe one or more patterns, along with tools which create and consume these patterns. Most patterns will just be a description of a sensible way to use existing classes & predicates.
(open to negotiation & common sense, of course)
- Examples should be given in RDF+XML.
- RDF+XML examples should not use nested resources, except for bnodes.
- Resources should always be <rdf:Description>. Express types using <rdf:type> not the shortcut XML way.
<strike>tags to indicate examples of bad patterns which are not intended to be copied, but rather to serve as warnings.
- Some schemas have pairs of inverse predicates. Each recipe should pick one or the other and use only that throughout.
- Try and use the predicates used by other OpenOrg recipes, where it makes sense to do so.
- Use "dct:" as the prefix for "DC-Terms". Don't use dc-elements at all.
- For namespaces, use the prefix from http://prefix.cc/
- Define a general recipe and then give extensions for use in specific types of organisation (eg. Universities, Publishers, charities)
- (idea) Include recommended CONSTRUCT statements to use when importing the basic data into SPARQL to add the inverse predicates, etc.
Types of pattern:
Also you can mark things as a suspected or established Antipattern - This pattern has been tried and caused unexpected problems. Established means more than one group tried it and agrees it was a bad solution.
MediaWiki has been successfully installed.
Consult the User's Guide for information on using the wiki software.