WordPress.org

Making WordPress.org

Opened 19 months ago

Closed 19 months ago

Last modified 19 months ago

#3628 closed defect (invalid)

Namespace URLs in export files are broken links

Reported by: jblz Owned by:
Milestone: Priority: normal
Component: General Keywords:
Cc:

Description

When performing a standard WordPress export, the resultant file ends up with a couple of lines like this:

	xmlns:excerpt="http://wordpress.org/export/1.2/excerpt/"
	xmlns:wp="http://wordpress.org/export/1.2/"

Both of the above links result in a 404.

They're generated during the export here.

It doesn't seem to adversely affect the import process using the standard importer plugin, but the schema should be accessible.

It's likely just a minor server configuration issue.

Change History (2)

#1 @Otto42
19 months ago

  • Resolution set to invalid
  • Status changed from new to closed

Those are XML namespaces, not URLs or links.

https://en.wikipedia.org/wiki/XML_namespace

Just because a thing starts with 'http' doesn't mean that it needs to be a valid location. It is an identifier. It resides in a domain that we have control over (wordpress.org) so that we know that it will be consistent and will not change.

https://en.wikipedia.org/wiki/XML_namespace#Namespace_names

A namespace name is a uniform resource identifier (URI). Typically, the URI chosen for the namespace of a given XML vocabulary describes a resource under the control of the author or organization defining the vocabulary, such as a URL for the author's Web server. However, the namespace specification does not require nor suggest that the namespace URI be used to retrieve information; it is simply treated by an XML parser as a string. For example, the document at http://www.w3.org/1999/xhtml itself does not contain any code. It simply describes the XHTML namespace to human readers. Using a URI (such as "http://www.w3.org/1999/xhtml") to identify a namespace, rather than a simple string (such as "xhtml"), reduces the probability of different namespaces using duplicate identifiers.

#2 @jblz
19 months ago

Thanks, @Otto42. That makes sense.

Note: See TracTickets for help on using tickets.