initial commit

Attempted to setup a basic architecture that could work across frameworks and
formats.

Intended as a discussion starter!
No on controllers. There are 3 packages, CollectionJson is just an object
model, nothing more. The web API stuff is in CollectionJson.Server.
CollectionJson itself does not need to be touched.
On Wed, Dec 3, 2014 at 9:13 AM Geoffrey Braaf <notifications@github.com>
wrote:

> In
> src/DotNetHypermedia/DotNetHypermedia.CollectionJson/CollectionJsonResourceConverter.cs:
>
> > @@ -0,0 +1,21 @@
> > +﻿using System;
> > +
> > +namespace DotNetHypermedia.CollectionJson
>
> Well, probably, i mean that than. But, in order to be able to define an
> abstraction for converters, a common abstraction (interface/abstract class)
> is required across all format specific resource objects. Unless we depend
> on the suggested library or change it to depend on HyperMediaDotNet i do
> not see that working.
>
> I was under the impression that the mentioned library would in some for or
> shape get pulled into the HypermediaDotNet effort. Using it alongside
> HypermediaDotNet won't work imho as the library requires controller and
> returned-object specific implementations, right?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/DotNetHypermedia/DotNetHypermedia/pull/15/files#r21247242>
> .
>