Main Page

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.

Wiki? Not quite! We are using a wiki to run this site but with only a very limited number of editors.

Open Orgs Recipe Book

New to RDF/Linked Data/Semantic Web? Read the: Linked Data Basics for Techies Proposed Recipes Boilerplate recommended data to include in any RDF document provided by your organisation. Organisational Structure Event Programmes http://programme.ecs.soton.ac.uk - has been used by SemHE, Web Science Trust & Ventnor Fringe (all produced by Christopher Gutteridge). Site provides source for a tool to process the format into HTML and iCal. Points of Service or Sale including coffee shops, photocopy points, carparks etc. Facilities and Equipment for describing major items of equipment and facilities (and services) of an organisation such as a university. Desired / Work-in-progress Top Level -- data about the organisation itself Data Catalogue -- a list of datasets available from an organisation Identifiers Phonebook - FOAF? Publications Research - BIBO/EPrints. Books Music Book Publisher Places - Open Org Places. Room features and configurations Tenders Products http://www.heppnetz.de/projects/goodrelations/ - GoodRelations Social media Spending http://data.gov.uk/resources/payments Menus (food, drink etc.) GoodRelations + oo extensions Courses eg. as offered by a university or similar. aiiso, rkb courseware Press Information Energy Useage Travel Timetables Vacancies Tools OpenOrg Grinder Publishing Techniques Flat RDF Documents SPARQL One RDF Document per Dataset One RDF Document per Record Follow your nose

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. If you want to add or contribute, please read the Cookbook Guidelines first (open to negotiation and common sense) Types of pattern: Desired - someone would like there to be a pattern but nobody has proposed one yet Proposed - a straw man for discussion Established - must satisfy ALL of the conditions at least one organistion provides open data in this pattern at least one free tool produces this pattern at least one free tool understands this pattern Mature - must satisfy ALL of the conditions at least three organistions provides open data in this pattern (sites run by the same group don't count) at least one free tool produces this pattern at least one free tool understands this 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.