pragmatic_context 0.1.3 → 0.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a60bf7a2275e2574efef334b737bd33f8f906257
-  data.tar.gz: 7af80e83673d61cfa2878280783ac29fd0be7bf5
+  metadata.gz: c352301219972a3d0b5ede9d37a007b2e7a22e53
+  data.tar.gz: 3bf10c2fc0b49085b3bed5bd548500ed4cff75ee
 SHA512:
-  metadata.gz: 00e267df94129526296bd61a1e810b45c87c29e71121f95deb93272a8203ebfade3f94750746f4eaace246ba0afdb2d450bc6ace4f65421471c472468f414fd5
-  data.tar.gz: fb7bbae5beda4427d6ca15551ce7aa01a3782e21e03dc3bdf992d3f50aebc29e6c2d61eb01b2c862657f111d114acb87ddea6f46450a45e18dad97f3823249ff
+  metadata.gz: 80dc5647ef9ed86d8461e6fedd69358ffff62f63be17326f295d10e79b5f9dfe4162a2e0dd0f04b621e7a68ee7c6112e9c0ac299597a0c1683b6a380f4c8a52d
+  data.tar.gz: 06ed957154e5c9be3f5dd231284178dc931d392064977dbba4b2a55eab298e0fe79283a7770f3368403692646c37373af8d0917627b526a4662f48149e58e2c5

data/README.md

@@ -10,7 +10,7 @@ I'm glad you asked. [JSON-LD](http://json-ld.org/) is a lightweight JSON format
 for expressing data within a context (also known as 'Linked Data'). Essentially
 what this means is that it lets you say that the thing your data model calls
 a 'last_name' (and what someone else may call 'family_name', or 'surname', or 'apellido') are all embodiments of the same abstract idea of a [Family
-Name](http://xmlns.com/foaf/spec/#term_familyName). JSON-LD is similar in spirit
+Name](http://schema.org/familyName). JSON-LD is similar in spirit
 (though [vastly different in
 execution](http://manu.sporny.org/2014/json-ld-origins-2/)) to
 [RDF](http://en.wikipedia.org/wiki/Resource_Description_Framework). It allows
@@ -51,7 +51,7 @@ identify a field as representing the concept of a person's first
 name, whether the field was named 'first_name', 'FirstName', 'given_name', or
 even 'field1234'. By allowing you to contextualize your data, JSON-LD lets you
 essentially say "when I say 'last_name', I really mean
-`http://xmlns.com/foaf/0.1/familyName`". In so doing, it becomes possible to
+`http://schema.org/familyName`". In so doing, it becomes possible to
 associate the last name fields of any JSON-LD API, regardless of what they name
 their fields.
 

data/lib/pragmatic_context/default_contextualizer.rb

@@ -15,10 +15,14 @@ module PragmaticContext
     private
 
     def definition_from_params(params)
-      result = {}
-      result['@id'] = params[:as] if params[:as]
-      result['@type'] = params[:type] if params[:type]
-      result
+      if params.keys == ['as']
+        params[:as]
+      else
+        result = {}
+        result['@id'] = params[:as] if params[:as]
+        result['@type'] = params[:type] if params[:type]
+        result
+      end
     end
   end
 end

data/lib/pragmatic_context/version.rb

@@ -1,3 +1,3 @@
 module PragmaticContext
-  VERSION = "0.1.3"
+  VERSION = "0.1.4"
 end

data/spec/lib/pragmatic_context/default_contextualizer_spec.rb

@@ -3,11 +3,11 @@ require 'pragmatic_context/default_contextualizer'
 describe PragmaticContext::DefaultContextualizer do
   describe 'adding terms' do
     it 'should add terms and be able to retrive them' do
-      subject.add_term('bacon', :as => 'http://bacon.com')
+      subject.add_term('bacon', :as => 'http://bacon.com', :type => 'number')
       subject.add_term('ham', :as => 'http://ham.com')
       subject.definitions_for_terms(%w(bacon ham)).should eq({
-        "bacon" => { "@id" => "http://bacon.com" },
-        "ham" => { "@id" => "http://ham.com" } 
+        "bacon" => { "@id" => "http://bacon.com", "@type" => "number" },
+        "ham" => "http://ham.com"
       })
     end
   end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pragmatic_context
 version: !ruby/object:Gem::Version
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors:
 - Mat Trudel
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-07-02 00:00:00.000000000 Z
+date: 2014-10-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler