[dotNetRDF-develop] RFC - Feature Requests/Bug Reports for upcoming 0.3.1 release

[Rob V. <rv...@do...>]

Hi All

I'm hoping to get the next release (0.3.1) made in the next couple of weeks 
so I'm solicitating any final feature requests/bug reports prior to this 
release.

Fixes and Changes for this release so far are as follows:

Added
- New RdfXmlWriter which is a streaming writer based on FastRdfXmlWriter
- New Writing.Formatting namespaces
 - Introduces ITripleFormatter, INodeFormatter, IUriFormatter and 
ICharFormatter interfaces
 - Provides an easy to use and reusable means of formatting nodes and 
triples
 - Refactored existing code to use formatters for writing
- New Parsing.Validation namespace
 - Provides simple classes for validating syntax
- SPARQL Views
 - Create Graphs which are dynamically generated from a SPARQL Query and 
updated when the underlying data changes/on demand
- Silverlight Compatability
 - Emulated HtmlTextWriter and HttpUtility for Silverlight compatability
 - Variety of compiler symbols defined to allow various library features to 
be disabled
 - SparqlXmlParser and SparqlXmlWriter use XmlReader and XmlWriter 
respectively when no XML DOM API available
 - TriXParser and TriXWriter use XmlReader and XmlWriter respectively when 
no XML DOM API available

Changed
- Bug Fixes
 - SqlTripleStore initialises correctly and persists updates correctly when 
used with an ISparqlUpdateProcessor
 - More intelligent parsing of Blank Node IDs from SPARQL Results
 - TriG Writer outputs all required @prefix definitions and generates 
consistent QNames
 - URI Loader Cache handles File IO errors gracefully
 - Rare forms of Numeric Literals now supported by Turtle, N3, TriG and 
SPARQL Parsers
 - Potentially ambigious QNames and Plain Literals now no longer cause 
parsing errors in Turtle, N3, TriG and SPARQL Parsers
- General Improvements
 - INamespaceMapper interface extracted and some visibility changes to 
NamespaceMapper methods
- SPARQL Improvements
 - Optimisations for ASK queries
 - Optimisations for CONSTRUCT/DESCRIBE/SELECT where LIMIT/OFFSET is used
- ASP.Net Improvements
 - Better caching support for BaseGraphHandler - now sends ETag in 
responses and may response with 304 Not Modified as appropriate

Removed
- Obsolete RdfXmlWriter removed

Please note that I am primarily only looking for issues that should be 
addressed for this next release.  These may be minor feature requests e.g. 
additional overloads of methods, error message improvements or bug reports 
for bugs that are not already covered in the above list.

Major feature requests are always welcome but obviously these will not be 
considered for the immediate next release, if you would like to make such a 
request please let us know and we'll reply as to whether such a feature 
can/will be included and a tentative timeline for such a feature.

Best Regards,
Rob Vesse