Tomasz Pluskiewicz

Currently the deserialiser is strict when deserialising literals. For example, `xsd:nonNegativeInteger` will not deserialise into an `int`, leaving the property with default value. Instead, if the string value can be...

Expand literals by default

1

fixes #3 fixes #9

Issue wikibus/Argolis#8 reveals that the documentation is incomplete. I should add an example of `IContextProvider` to the page about resolving `@context`

[Type] annotation for properties

9

The `TypeAttribute` proposed by @asbjornu (see #6) could also be used with properties to declare literal type: ``` c# [Type("xsd:date")] public DateTime BirthDate { get; set; } ``` would serialize...

Adding datatype explicitly

3

When a class is serialized `DateTime` values should include `@type` so that they can be interpreted correctly and not as `xsd:string`. _This could be an opt-in feature_. ``` c# public...

Add [Vocabulary] annotation

1

As suggested by @asbjornu, it will be good to give users an option to define `@vocab` using an attribute instead of defining it in the `@context`: ``` c# [Vocabulary("http://schema.org/")] public...

As suggested by @asbjornu, it will be good to give users an option to define `@type` using an attribute. Of course multiple would have to be allowed. ``` c# [Type("http://schema.org/Person")]...

The serializer should ensure that the context contains a given key. - [ ] check a key named as the propety exists - [ ] check correct `@container` set for...

I found that in a case when only a subset of columns are actually mapped, the default columns would not be output but instead a "random" predicate from the those...

I found that templates were incorrectly produced, cells being not fully encoded as per RFC3986. For example, parentheses were not percent-encoded, likely being done by JS' flawed implementation of `encodeURIComponent`...