Your SlideShare is downloading. ×
Rapid semantic web app dev using Callimachus
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Rapid semantic web app dev using Callimachus

985
views

Published on

Semantic Content Management framework with wiki interface for creating data-driven Web applications. This is an Open Source project based on International Data Exchange standards (W3C) and Web …

Semantic Content Management framework with wiki interface for creating data-driven Web applications. This is an Open Source project based on International Data Exchange standards (W3C) and Web technologies. Learn more about Callimachus at http://callimachusproject.org.

Published in: Technology, Education

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
985
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 3 Round Stones has since purchased the US division of Talis James Leigh and we are going to talk about Rapid SemWeb App Dev New approach to Software development - steeper requirements than it did a decade ago Information overload, Impatient society, Change is the only constant Software is not valued by its usefulness, but by its expected future value
  • Need a solution that will be up and running today Handle the change coming tomorrow Guide editors to collect and structure their data
  • Creating, Updating, Correcting, Collecting, Annotating, Publishing, Categorizing Curation gives an overall structure to reveal relationships about resources
  • A few different possible solutions to the three challenges stated earlier
  • Emerged in the 1990s from a need to scale middle ware separately from the database
  • Historically an entire user session may have been performed in isolation Long pessimistic transactions don't scale On the Web optimistic mechanisms are common place
  • 3TA requires experienced software professionals to make even the simplest of changes Unless there is a team of software engineers ready to make changes, software is worthless Three tier architecture is expensive and is only viable in broad markets
  • The big downside to 3TA is the upfront cost So we then looked at CMS These are systems that can be up and running the same day
  • CMS has a significant reduced upfront cost Like 3TA change and customization is expensive General CMS do not quickly adapt to change
  • CMS are slow to adopt to change So we then looked at Wiki Systems. These are open ended, put whatever you want in them
  • When presented with infinite choice, it's sometimes hard to get started How do you ask multiple editors to provide particular information consistently?
  • Wiki Systems don't handle structured content well nor promulgate change well. A tool for Web 2.0 developers interested in the power of Linked Data was needed … We created Callimachus, a LINKED DATA MANAGEMENT SYSTEM. 100% triples inside & out. Based on an increasingly popular international data exchange standard, RDF (RDF/XML, Turtle, etc) Callimachus stores data in a flexible RDF store. This greatly reduces development and maintenance costs
  • Callimachus is a great way to collaboratively manage your linked data Wikimedia is to free text what Callimachus is to linked data
  • Callimachus can get you started today, adapt to change tomorrow, and help you structure your data
  • The Callimachus project is named after a Greek poet and librarian He was the first person in history to reject hierarchical categorization He needed this software 2300 years ago, unfortunately, we are a bit late getting it to him
  • Callimachus incorporates many of the content and collaborative functionality from wiki systems
  • Callimachus differs from wikis because of its structured form for editing resources This helps guide editors to provide meaningful information
  • Callimachus uses a straight forward ACL for linked data
  • Every change through the browser is tracked Triples all the way down
  • Page and form templates are assigned to RDF class hierarchy
  • This is a vanilla Callimachus instance. It happens to be a for financial system proof of concept.
  • This is an example of a Callimachus template form for editing a person, in this case Bernadette Hyland.
  • This screen shows the wiki like editing user interface. What is cool about this is that you are creating RDF triples, structured content, and this is completely invisible to the person using what they feel is an easy to use wiki for content creation …
  • Callimachus also integrates visualization capabilities, using Google charts. Other visualizations including time series, bar charts, map views, etc are supported too.
  • Transcript

    • 1. Rapid Semantic Web Application Development This talk previously given at SemTech 2011, San Francisco By James Leigh
    • 2. Problem Statement
      • Start curating data today
      • Data model may change tomorrow
      • Guided curation
      • Web based solution
    • 3. Data Curation
      • Data management
      • Adding value to data
      • Data sharing for re-use
      • Data preservation
    • 4. Possible Solutions
      • Roll your own three-tier
      • Content Management System
      • Wiki-based
      • Linked Data Management System
    • 5. Three Tier Architecture
      • Easier to replace any single tier
      • Separation for better load balancing
      • Secure database independently
    • 6. Three Tier Architecture
      • Designed for pessimistic databases that are hard to scale horizontally
      • Optimistic layered over pessimistic mechanism
      • High upfront costs
      • Rigid schema
    • 7. Three Tier Architecture
      • Data model changes affect all tiers
        • Change your presentation
        • Change your processing model
        • Change your data schema
    • 8. Ten Points of Failure
      • Multiple programming paradigms
      • Multiple data models
        • XML/JSON, markup, form,
        • ORM, OOP, parameters,
        • Query/Update and schema
    • 9. Content Management Systems
      • Wordpress
      • Drupal
      • Joomla!
    • 10. Content Management System
      • Collaboratively share data
      • Control access
      • Easy storage
      • Reduce duplicate
      • Improve report writing
      • Improve communication
    • 11. Content Management System
      • Many features out of the box
      • Compile time extendable
      • Rigid data model
    • 12. Wiki Software
      • Media Wiki
      • Semantic Media Wiki
    • 13. Wiki Software
      • Collaboratively edit web pages
      • Transparency, linking, and a low barrier to entry
      • Wikis focus on the content
    • 14. Wiki Software
      • Many features out of the box
      • Easy to add new content data
      • Unstructured data
      • Blank page syndrome
    • 15. Linked Data Management System
      • Allows Web 2.0 developers to build structured hyper linked web applications using a flexible schema
    • 16. Linked Data Management System
      • Easily build hyper linked Web applications
        • Edit Content
        • Access Control
        • Collaboration
        • Change Tracking
        • Page/form Templates
    • 17. Linked Data Management System
      • Some features out of the box
      • Deals with structured data (triples up and down)
      • Run time extendable
      • Custom data model
    • 18. Καλλίμαχος of Cyrene
      • 305-c. 240 BCE
      • Father of Bibliography (The Pinakes) at the Great Library of Alexandria
      • Could not categorize his own work in Aristotle's hierarchical system
    • 19. Web Content
      • What-You-Mean Editor
      • Separates visual presentation and content
      • Edit according to meaning and significance
        • Not appearance
    • 20. Easily Edit Resources
      • Structured guided resource editing
      • Reduce learning curve
      • Lower contribution barrier
    • 21. Access Control
      • Permissions set on
        • Resource class
        • Individual resource
      • ACL for
        • Readers
        • Contributors
        • Editors
        • Administrators
      • Permissions propagate to nested resources
    • 22. Collaboration
      • Discussion form on every resource
      • Change tracking
      • List of who made each change on every resource
    • 23. Page/Form Builder
      • Easy to change
        • Class hierarchy
        • Edit resource layout
        • Create resource forms
    • 24.  
    • 25.  
    • 26.  
    • 27.  
    • 28. Please give us your feedback
      • Callimachus has benefited from 2+ years of corporate support.
      • We’re using it for real world Web applications in environmental protection, finance and healthcare
      • Open Source community project
      • Visit callimachusproject.org
      • Join the discussion

    ×