Standard: Consider adding support for XSLT, XPath and XQuery v3

[DanAtkinson]

It's been many years since 1.0 was added to the .NET Framework in v2. Over the years, Microsoft has continually refused (read: declined to implement) any of the future versions of the spec without providing much of a reason.

Looking at the FAQ page you mention JSON.NET as not being included in .NET Standard because it would do the community a disservice. I would agree here as there are extremely competent providers of JSON handling. However, the same cannot be said for XSLT/XPath/XQuery.

The last UserVoice issue for it was opened 3.5 years ago and you have done the community a disservice by not acknowledging the clear demand for it.

I would therefore ask that you consider adding support for it in a future version of .NET Standard.

Thank you.

[svick]

The .Net Standard is not the right place to ask for changes in APIs. Those changes should first happen in one of the implementations (usually .Net Core) and then be accepted to the standard. See this item in the FAQ.

So, API changes in the .Net Standard, should be proposed in the corefx repository. There's already an issue to update XPath (https://github.com/dotnet/corefx/issues/2295), which needs a proper proposal following the CoreFX API review process.

[weshaggard]

As @svick mentions this is best served in the corefx repo and we already have https://github.com/dotnet/corefx/issues/2295 tracking it so I'm closing this issue in favor of that one.