Feed off of catalog gen. schema def #1

Activity

1. rclark commented on Sep 20, 2013

   

   rclark

   on Sep 20, 2013

   More actions

   Is there a "canonical" location yet for the schema? It appears the schema.yml file no longer exists.
2. cew821 commented on Nov 18, 2013

   

   cew821

   on Nov 18, 2013

   Contributor

   More actions

   @dwcaraway is working on this, over in his Podschema repo https://github.com/dwcaraway/podschema using the json-schema. However I'm not sure how complete this is.
3. rclark commented on Nov 18, 2013

   

   rclark

   on Nov 18, 2013

   More actions

   fwiw this is what I came up with based on what I read on http://project-open-data.github.io/schema/ about 2 months ago.

   I built it as a function that returns a json-schema, allowing you to adjust the schema by giving you a way to require the "as-needed" or additional fields if they are in fact needed. You can also add new fields, if your application needs them, by passing them as "overrides". It won't let you make adjustments to the core required fields.
4. dwcaraway commented on Nov 18, 2013

   

   dwcaraway

   on Nov 18, 2013

   More actions

   neat idea, ryan!

   On Mon, Nov 18, 2013 at 3:44 PM, Ryan Clark notifications@github.comwrote:

   fwiw this is what I came up withhttps://github.com/rclark/project-open-catalog/blob/master/schema/openDataSchema.jsbased on what I read on
   http://project-open-data.github.io/schema/ about 2 months ago.

   I built it as a function that returns a json-schema, allowing you to
   adjust the schema by giving you a way to require the "as-needed" or
   additional fields if they are in fact needed. You can also add new fields,
   if your application needs them, by passing them as "overrides". It won't
   let you make adjustments to the core required fields.

   —
   Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-28736071
   .

   Dave Caraway
   Co-Founder
   Fogmine
   dave@fogmine.com
   Cell: (937) 985-0867
   Fax: (866) 238-3120
5. gbinal commented on Nov 23, 2013

   

   gbinal

   on Nov 23, 2013

   More actions

   @dwcaraway, @cew821, @benbalter, or @rclark - any interest in taking a whack at using the JSON schema files that Dave recently posted to Project Open Data to update and power this validator?
6. dwcaraway commented on Nov 24, 2013

   

   dwcaraway

   on Nov 24, 2013

   More actions

   this has been on my TODO list for...well weeks, anyways, I'll make some
   time to put it in place.

   On Sat, Nov 23, 2013 at 6:49 PM, Gray Brooks notifications@github.comwrote:

   @dwcaraway https://github.com/dwcaraway, @cew821https://github.com/cew821,
   @benbalter https://github.com/benbalter, or @rclarkhttps://github.com/rclark- any interest in taking a whack at using the
   JSON schema fileshttp://project-open-data.github.io/metadata-resources/#json-schema-filesthat Dave recently posted to Project Open Data to update and power this
   validator?

   —
   Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-29144883
   .

   Dave Caraway
   Co-Founder
   Fogmine
   dave@fogmine.com
   Cell: (937) 985-0867
   Fax: (866) 238-3120
7. rclark commented on Nov 24, 2013

   

   rclark

   on Nov 24, 2013

   More actions

   I really like the website-based validation for situations where you already have some docs, need them validated. I'm thinking ahead though to an application geared towards creating and maintaining an agency's set of metadata records. In that case, I'll need something that I can use programmatically. What if the validation process was a Node.js package? Could that be browserified to power this site?