Metadata validation needs to support <edmx:References>

Validator currently returns an error if the metadata contains an <edmx:References> element as a child of the <edmx:Edmx> element, where <edmx:References> is clearly valid in that context according ...

Id #41 | Release: None | Updated: Jan 13, 2015 at 10:32 PM by MikePizzo | Created: Jan 13, 2015 at 10:32 PM by MikePizzo

Expose Service Validator as a Service

It would be cool to expose the validator as a service so that people building OData services could add the validation step into their build toolchain. Offering a score and result set right next to...

Id #39 | Release: None | Updated: Sep 28, 2013 at 10:17 PM by drdamour | Created: Sep 28, 2013 at 10:17 PM by drdamour

Switch format options to multiple select

right now the format validation only allows one at a time. It would be better if you could just validate a service for any of it's possible formats. I suggest changing the radio boxes to checkbo...

Id #38 | Release: None | Updated: Sep 28, 2013 at 10:08 PM by drdamour | Created: Sep 28, 2013 at 10:08 PM by drdamour

ContextHelper.ToContentType should properly handle ;charset= in Content-Type

e.g. application/xml;charset=utf-8 should be mapped to PayloadFormat.Xml In general, the validator should handle Content-Type according to the odata spec 2.2.5.2

Id #37 | Release: None | Updated: Jun 17, 2012 at 10:37 PM by JohnSpurlock | Created: Jun 17, 2012 at 10:37 PM by JohnSpurlock

Http header field name should be case insensitive when definined in headerregex of XML rule

According to the HTTP spec (W3) field names are case insensitive. However the regex verify code in file HttpHeaderRegexVerifier.cs creates a case sensitive expression. Consider changing the code t...

Id #36 | Release: None | Updated: Mar 19, 2012 at 7:21 PM by hwche | Created: Mar 19, 2012 at 7:12 PM by hwche

Runtime exception while validating metadata document

Hi, A runtime exception is raised by the rule Common.core.2016 (Object reference not set to an instance of an object.) when validating the northwind service http://services.odata.org/Northwind/N...

Id #35 | Release: None | Updated: Feb 23, 2012 at 8:53 AM by d037672 | Created: Feb 23, 2012 at 8:53 AM by d037672

Sophisticated Accept header may lead to undesirable response

When atompub/xml is chosen at the validation page (default.html) as the format hint, the validation tool sends request having following Http header Accpet : /; q=0.2, application/atom+xml, applica...

Id #34 | Release: None | Updated: Nov 22, 2011 at 12:52 AM by hwche | Created: Nov 22, 2011 at 12:52 AM by hwche

Code rule - hardcoding or not: description / error message

Currently, description / error message is hard coded in the rules. Is there a better way to deal with this? For Better management.

Id #33 | Release: None | Updated: Nov 7, 2011 at 6:42 PM by jcyang75 | Created: Nov 7, 2011 at 6:42 PM by jcyang75

extensio rule lib: get values from key combination does not get the full set when (,= are embedded in the metadata uri property

looks like neither of chars of = ( ) , should be in keypredicate-cmplx in the first palce. Opened a P2 OIPI [MC-APDSU] bug 277749 asking for spec revision. Show Changes (Fields) 2.2.3.1, [MC-APD...

Id #32 | Release: None | Updated: Nov 7, 2011 at 6:40 PM by jcyang75 | Created: Nov 7, 2011 at 6:40 PM by jcyang75

Xslt dynamic rule constructor should do sanity check as early as possible

XsltJsonSchemaVerifier ctor accepts any string as xslt parameter. The error checking is deferred until runtime. Better to check error early; it is desirable to check xslt XSL-formed in ctor. It...

Id #31 | Release: None | Updated: Nov 7, 2011 at 6:38 PM by jcyang75 | Created: Nov 7, 2011 at 6:38 PM by jcyang75