Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XML Schemas in xaml files are not accessible #429

Open
Garfield550 opened this Issue Mar 9, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@Garfield550
Copy link

Garfield550 commented Mar 9, 2019

  • .NET Core Version: 3.0.100-preview4-010677
  • Windows version: 17763.316
  • Does the bug reproduce also in WPF for .NET Framework 4.8?: Yes

Problem description:

Links to XML Schemas in MainWindow.xaml (also in other XAML files) are dead.

Actual behavior:

dotnet new wpf -o longlivexml

Open any .xaml file, open the links (see below).

xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"

All of them can't be opened.

Expected behavior:

The links show XML Schemas.

Minimal repro:

See above.

@weltkante

This comment has been minimized.

Copy link

weltkante commented Mar 10, 2019

isn't this normal behavior? I always thought you just make up uris under your domain to avoid conflicts with 3rd parties but aren't obligated to actually publish anything under that uri.

Also, does a schema for xaml even exist? How would one describe the extensions it does over normal xml in the schema? I never saw any documentation of how to write xaml schemas, just that you use uris to disambiguate different namespaces ....

@watfordgnf

This comment has been minimized.

Copy link

watfordgnf commented Mar 12, 2019

Namespace names are URI's (IRI's as of XML 1.1), but there is no requirement that they be reachable if they happen to specify a protocol. From the XML 1.0 recommendations (emphasis mine):

The attribute's normalized value MUST be either a URI reference — the namespace name identifying the namespace — or an empty string. The namespace name, to serve its intended purpose, SHOULD have the characteristics of uniqueness and persistence. It is not a goal that it be directly usable for retrieval of a schema (if any exists). Uniform Resource Names [RFC2141] is an example of a syntax that is designed with these goals in mind. However, it should be noted that ordinary URLs can be managed in such a way as to achieve these same goals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.