gearbox 0.1.0

data/.document

@@ -0,0 +1,5 @@
+lib/**/*.rb
+bin/*
+- 
+features/**/*.feature
+LICENSE.txt

data/Gemfile

@@ -0,0 +1,21 @@
+source 'http://rubygems.org'
+
+gem 'linkeddata'
+gem 'rspec'
+gem 'uuid'
+
+if RUBY_PLATFORM =~ /darwin/i
+  gem 'autotest-fsevent'
+  gem 'autotest-growl'
+end
+
+group :development do
+  gem "minitest", ">= 0"
+  gem "yard", "~> 0.6.0"
+  gem "bundler"
+  gem "jeweler", "~> 1.6.4"
+  gem "simplecov", ">= 0"
+  gem 'guard-markdown'
+  gem "ruby-debug19"
+  gem 'guard-minitest', :git => 'git://github.com/aspiers/guard-minitest.git'
+end

data/Gemfile.lock

@@ -0,0 +1,138 @@
+GIT
+  remote: git://github.com/aspiers/guard-minitest.git
+  revision: 4b660261d3596b7dd2a9fe135f7ee23ca0c04cc1
+  specs:
+    guard-minitest (0.4.0)
+      guard (~> 0.4)
+
+GEM
+  remote: http://rubygems.org/
+  specs:
+    addressable (2.2.7)
+    archive-tar-minitar (0.5.2)
+    autotest-fsevent (0.2.8)
+      sys-uname
+    autotest-growl (0.2.16)
+    backports (2.3.0)
+    columnize (0.3.6)
+    diff-lcs (1.1.3)
+    ffi (1.0.11)
+    git (1.2.5)
+    guard (0.10.0)
+      ffi (>= 0.5.0)
+      thor (~> 0.14.6)
+    guard-markdown (0.1.4)
+      guard (>= 0.2.2)
+      kramdown (~> 0.13.3)
+    haml (3.1.4)
+    htmlentities (4.3.1)
+    jeweler (1.6.4)
+      bundler (~> 1.0)
+      git (>= 1.2.5)
+      rake
+    json (1.6.5)
+    json-ld (0.1.0)
+      json (>= 1.5.1)
+      rdf (>= 0.3.4)
+    json_pure (1.6.5)
+    kramdown (0.13.5)
+    linecache19 (0.5.12)
+      ruby_core_source (>= 0.1.4)
+    linkeddata (0.3.5)
+      json-ld (>= 0.1.0)
+      rdf (>= 0.3.5)
+      rdf-isomorphic (>= 0.3.4)
+      rdf-json (>= 0.3.0)
+      rdf-microdata (>= 0.2.3)
+      rdf-n3 (>= 0.3.6)
+      rdf-rdfa (>= 0.3.9)
+      rdf-rdfxml (>= 0.3.5)
+      rdf-trig (>= 0.1.1)
+      rdf-trix (>= 0.3.0)
+      rdf-turtle (>= 0.1.1)
+    macaddr (1.5.0)
+      systemu (>= 2.4.0)
+    minitest (2.11.3)
+    multi_json (1.1.0)
+    nokogiri (1.5.0)
+    rake (0.9.2.2)
+    rdf (0.3.5)
+      addressable (>= 2.2.6)
+    rdf-isomorphic (0.3.4)
+      rdf (>= 0.2.3)
+    rdf-json (0.3.0)
+      json_pure (>= 1.4.2)
+      rdf (~> 0.3.0)
+    rdf-microdata (0.2.3.1)
+      htmlentities (>= 4.3.0)
+      json (>= 1.6.1)
+      rdf (>= 0.3.4)
+      rdf-xsd (>= 0.3.4)
+    rdf-n3 (0.3.6)
+      rdf (>= 0.3.4)
+    rdf-rdfa (0.3.9)
+      backports
+      haml (>= 3.0.0)
+      htmlentities (>= 4.3.0)
+      rdf (>= 0.3.3)
+      rdf-xsd (>= 0.3.5)
+    rdf-rdfxml (0.3.5)
+      nokogiri (>= 1.4.4)
+      rdf (>= 0.3.4)
+    rdf-trig (0.1.1)
+      rdf (>= 0.3.4)
+      rdf-turtle (>= 0.1.1)
+    rdf-trix (0.3.0)
+      rdf (~> 0.3.0)
+    rdf-turtle (0.1.1)
+      rdf (>= 0.3.4)
+    rdf-xsd (0.3.5)
+      nokogiri (>= 1.5.0)
+      rdf (>= 0.3.4)
+    rspec (2.8.0)
+      rspec-core (~> 2.8.0)
+      rspec-expectations (~> 2.8.0)
+      rspec-mocks (~> 2.8.0)
+    rspec-core (2.8.0)
+    rspec-expectations (2.8.0)
+      diff-lcs (~> 1.1.2)
+    rspec-mocks (2.8.0)
+    ruby-debug-base19 (0.11.25)
+      columnize (>= 0.3.1)
+      linecache19 (>= 0.5.11)
+      ruby_core_source (>= 0.1.4)
+    ruby-debug19 (0.11.6)
+      columnize (>= 0.3.1)
+      linecache19 (>= 0.5.11)
+      ruby-debug-base19 (>= 0.11.19)
+    ruby_core_source (0.1.5)
+      archive-tar-minitar (>= 0.5.2)
+    simplecov (0.6.1)
+      multi_json (~> 1.0)
+      simplecov-html (~> 0.5.3)
+    simplecov-html (0.5.3)
+    sys-uname (0.9.0)
+      ffi (>= 1.0.0)
+    systemu (2.4.2)
+    thor (0.14.6)
+    uuid (2.3.5)
+      macaddr (~> 1.0)
+    yard (0.6.8)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  autotest-fsevent
+  autotest-growl
+  bundler
+  guard-markdown
+  guard-minitest!
+  jeweler (~> 1.6.4)
+  linkeddata
+  minitest
+  rspec
+  ruby-debug19
+  simplecov
+  uuid
+  yard (~> 0.6.0)

data/Guardfile

@@ -0,0 +1,9 @@
+guard 'markdown', :convert_on_start => true, :dry_run => false do  
+  watch (/README.md/) {|m| "README.md|./README.html"}
+end
+
+guard 'minitest' do
+  watch(%r|^spec/(.*)_spec\.rb|)
+  watch(%r|^lib/(.*)\.rb|)            { |m| "spec/#{m[1]}_spec.rb" }
+  watch(%r|^spec/spec_helper\.rb|)    { "spec" }
+end

data/LICENSE.txt

@@ -0,0 +1,20 @@
+Copyright (c) 2012 David Richards
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.html

@@ -0,0 +1,89 @@
+<h1 id="gearbox">Gearbox</h1>
+
+<p>The purpose of this project is to make it easier for me to curate semantic graphs.  I&rsquo;m looking for deeper satisfaction in my personal research.  I tend to fill my days researching technology, market dispositions, and my own business documents.  These types of data stores, of course, could be applied in many areas.</p>
+
+<p>To get to wherever I am now, I&rsquo;ve been playing with semantic models for a while.  I started by demonstrating working code from various corners of my imagination.  After a while, I thought I had enough to create a useful gem.  In the past, I&rsquo;ve worked with <a href="https://github.com/bhuga/spira">Spira</a> and examples given by <a href="http://greggkellogg.net/">Gregg Kellogg</a>.  These have been very useful in forming ideas.</p>
+
+<p>As I worked on this code, I decided to go to <a href="https://github.com/bhuga/spira">Spira</a> to see how similar the two gems are.  I was surprised how similar they actually are.  The similarities are:</p>
+
+<ul>
+  <li>both are ORMs for semantic data, written in Ruby</li>
+  <li>support for properties/attributes</li>
+  <li>concept of model associations</li>
+  <li>data validations</li>
+  <li>value types</li>
+</ul>
+
+<p>However, Gearbox is quite a bit different.  It came from a different place.  I&rsquo;ve been trying to embrace the nature of semantic models.  This, juxtaposed against relational models or other types of models.  The major differences, I imagine are:</p>
+
+<ul>
+  <li>support for SPARQL-based scopes and finder methods</li>
+  <li>better support for working with various SPARQL end points</li>
+  <li>creating and maintaining full-text indices</li>
+  <li>object factory from triples</li>
+</ul>
+
+<h1 id="development-workflow-for-semantic-data">Development Workflow for Semantic Data</h1>
+
+<p>For a typical domain, I test-drive some models to define the nature of the data.  These are custom-built to support the user scenarios and behavior an application is built to serve.  For semantic models, I&rsquo;m going for something different.  The relationships between resources are much more dynamic.  It&rsquo;s tough to build an application on dynamic domain models.  </p>
+
+<p>To work with this, I&rsquo;d rather optimize for different things.  Instead of trying to canonize the data, concretize the interaction.  Given a head/buffer/file full of data, what&rsquo;s the easiest way to save it?  Which values have to be recorded?  Which values can be inferred or classified offline?  </p>
+
+<p>I think that there&rsquo;s going to be an evolution of the data graph.  I&rsquo;m looking to start with the mundane, and hope to be able to create a broad view from the details collected.  Possibly, I will have alternative broad views, such as a full view of the topic or a chronological account of the topic as it transpires.  From here, I want to look for insightful information: inferences that show the nature of our subject.  </p>
+
+<p>That&rsquo;s the goal.</p>
+
+<p>Practically, the work changes over time.  We start with defining the attributes and associations that are needed.  This is the mundane.  We then start to qualify the data by writing validations.  Probably, there will be overlapping models to reflect the interaction.  For example, browsing email might have a cursory recording of the people involved.  Looking up Twitter information might have a more-specific user model.  Facebook, the same.  We&rsquo;re building a summary of the users, or whatever we&rsquo;re studying.  From here, we might be able to use various analytical methods to classify and enhance the models, to clarify the story we are able to gather.</p>
+
+<p>As you can see, this is a very different process than something we might do with typical relational data.  I don&rsquo;t think there is much that we do with semantic data that can&rsquo;t be done with relational data, it&rsquo;s just that the technologies are optimized for different purposes.</p>
+
+<h1 id="practical-example">Practical Example</h1>
+
+<p>It would be good to offer a practical example.  I&rsquo;ll get to these in a bit.  I don&rsquo;t need to have the documentation get ahead of the released code.</p>
+
+<h1 id="todo">TODO</h1>
+
+<ul>
+  <li>bring in the association and combination code</li>
+  <li>implement mutability</li>
+  <li>implement persistence</li>
+  <li>implement queryable</li>
+  <li>implement named scopes</li>
+  <li>implement some sort of repository access</li>
+  <li>use Gearbox in the examples (were written to concretize an example in my head)</li>
+</ul>
+
+<h1 id="contributing-to-gearbox">Contributing to Gearbox</h1>
+
+<ul>
+  <li>Check out the latest master to make sure the feature hasn&rsquo;t been implemented or the bug hasn&rsquo;t been fixed yet</li>
+  <li>Check out the issue tracker to make sure someone already hasn&rsquo;t requested it and/or contributed it</li>
+  <li>Fork the project</li>
+  <li>Start a feature/bugfix branch</li>
+  <li>Commit and push until you are happy with your contribution</li>
+  <li>Make sure to add tests for it. This is important so I don&rsquo;t break it in a future version unintentionally.</li>
+  <li>Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.</li>
+</ul>
+
+<h1 id="copyright">Copyright</h1>
+
+<p>Copyright (c) 2012 David Richards</p>
+
+<p>Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+&ldquo;Software&rdquo;), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:</p>
+
+<p>The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.</p>
+
+<p>THE SOFTWARE IS PROVIDED &ldquo;AS IS&rdquo;, WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>

data/README.md

@@ -0,0 +1,87 @@
+Gearbox
+=======
+
+The purpose of this project is to make it easier for me to curate semantic graphs.  I'm looking for deeper satisfaction in my personal research.  I tend to fill my days researching technology, market dispositions, and my own business documents.  These types of data stores, of course, could be applied in many areas.
+
+To get to wherever I am now, I've been playing with semantic models for a while.  I started by demonstrating working code from various corners of my imagination.  After a while, I thought I had enough to create a useful gem.  In the past, I've worked with [Spira](https://github.com/bhuga/spira) and examples given by [Gregg Kellogg](http://greggkellogg.net/).  These have been very useful in forming ideas.
+
+As I worked on this code, I decided to go to [Spira](https://github.com/bhuga/spira) to see how similar the two gems are.  I was surprised how similar they actually are.  The similarities are:
+
+* both are ORMs for semantic data, written in Ruby
+* support for properties/attributes
+* concept of model associations
+* data validations
+* value types
+
+However, Gearbox is quite a bit different.  It came from a different place.  I've been trying to embrace the nature of semantic models.  This, juxtaposed against relational models or other types of models.  The major differences, I imagine are:
+
+* support for SPARQL-based scopes and finder methods
+* better support for working with various SPARQL end points
+* creating and maintaining full-text indices
+* object factory from triples
+
+Development Workflow for Semantic Data
+======================================
+
+For a typical domain, I test-drive some models to define the nature of the data.  These are custom-built to support the user scenarios and behavior an application is built to serve.  For semantic models, I'm going for something different.  The relationships between resources are much more dynamic.  It's tough to build an application on dynamic domain models.  
+
+To work with this, I'd rather optimize for different things.  Instead of trying to canonize the data, concretize the interaction.  Given a head/buffer/file full of data, what's the easiest way to save it?  Which values have to be recorded?  Which values can be inferred or classified offline?  
+
+I think that there's going to be an evolution of the data graph.  I'm looking to start with the mundane, and hope to be able to create a broad view from the details collected.  Possibly, I will have alternative broad views, such as a full view of the topic or a chronological account of the topic as it transpires.  From here, I want to look for insightful information: inferences that show the nature of our subject.  
+
+That's the goal.
+
+Practically, the work changes over time.  We start with defining the attributes and associations that are needed.  This is the mundane.  We then start to qualify the data by writing validations.  Probably, there will be overlapping models to reflect the interaction.  For example, browsing email might have a cursory recording of the people involved.  Looking up Twitter information might have a more-specific user model.  Facebook, the same.  We're building a summary of the users, or whatever we're studying.  From here, we might be able to use various analytical methods to classify and enhance the models, to clarify the story we are able to gather.
+
+As you can see, this is a very different process than something we might do with typical relational data.  I don't think there is much that we do with semantic data that can't be done with relational data, it's just that the technologies are optimized for different purposes.
+
+Practical Example
+=================
+
+It would be good to offer a practical example.  I'll get to these in a bit.  I don't need to have the documentation get ahead of the released code.
+
+TODO
+====
+
+* bring in the association and combination code
+* implement mutability
+* implement persistence
+* implement queryable
+* implement named scopes
+* implement some sort of repository access
+* use Gearbox in the examples (were written to concretize an example in my head)
+
+Contributing to Gearbox
+=======================
+ 
+* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
+* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
+* Fork the project
+* Start a feature/bugfix branch
+* Commit and push until you are happy with your contribution
+* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
+* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
+
+Copyright
+=========
+
+Copyright (c) 2012 David Richards
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/Rakefile

@@ -0,0 +1,46 @@
+# encoding: utf-8
+
+require 'rubygems'
+require 'bundler'
+begin
+  Bundler.setup(:default, :development)
+rescue Bundler::BundlerError => e
+  $stderr.puts e.message
+  $stderr.puts "Run `bundle install` to install missing gems"
+  exit e.status_code
+end
+require 'rake'
+
+require 'jeweler'
+Jeweler::Tasks.new do |gem|
+  # gem is a Gem::Specification... see http://docs.rubygems.org/read/chapter/20 for more options
+  gem.name = "gearbox"
+  gem.homepage = "http://github.com/davidrichards/gearbox"
+  gem.license = "MIT"
+  gem.summary = %Q{Flexible semantic models.}
+  gem.description = %Q{A SPARQL-driven modeling toolset for semantic models.}
+  gem.email = "davidlamontrichards@gmail.com"
+  gem.authors = ["David Richards"]
+  # dependencies defined in Gemfile
+end
+Jeweler::RubygemsDotOrgTasks.new
+
+require 'rake/testtask'
+Rake::TestTask.new(:test) do |test|
+  test.libs << 'lib' << 'test'
+  test.pattern = 'test/**/test_*.rb'
+  test.verbose = true
+end
+
+# require 'rcov/rcovtask'
+# Rcov::RcovTask.new do |test|
+#   test.libs << 'test'
+#   test.pattern = 'test/**/test_*.rb'
+#   test.verbose = true
+#   test.rcov_opts << '--exclude "gems/*"'
+# end
+
+task :default => :test
+
+require 'yard'
+YARD::Rake::YardocTask.new

data/VERSION

@@ -0,0 +1 @@
+0.1.0

data/lib/examples/audience.rb

@@ -0,0 +1,24 @@
+module Gearbox
+  class Audience
+    
+    attr_writer :resource_source
+
+    attr_accessor :name
+    
+    def add_resource(hash={})
+      new_resource = resource_source.call(hash.merge(:audience => self))
+      resources << new_resource
+      new_resource
+    end
+    
+    def resources
+      @resources ||= []
+    end
+    
+    private
+      def resource_source
+        @resource_source ||= Resource.public_method(:new)
+      end
+      
+  end
+end