Closed benlk closed 6 years ago
The NPRML Namespace is xmlns:nprml=https://api.npr.org/nprml, but https://api.npr.org/nprml does not have a schema. Is this intentional?
xmlns:nprml=https://api.npr.org/nprml
The present version of the w3c recommendation for Namespaces in XML 1 doesn't require that the namespace URI reference be a link to an active schema doc:
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).
The entire document at https://api.npr.org/nprml is as follows:
{"error":"This API is not found. For documentation of current API services, please visit the NPR Developer Center."}
https://api.npr.org/ 301 redirects to https://www.npr.org/api/index.
And, should this URL be upgraded to HTTPS?
https://github.com/npr/nprapi-wordpress/blob/f4032ce35af448a9800f6412884f483ca986819f/classes/NPRAPI.php#L21
Upgrading to HTTPS in #44.
Closing because the namespace link does not need to return a schema, according to the relevant XML specification.
The NPRML Namespace is
xmlns:nprml=https://api.npr.org/nprml
, but https://api.npr.org/nprml does not have a schema. Is this intentional?The present version of the w3c recommendation for Namespaces in XML 1 doesn't require that the namespace URI reference be a link to an active schema doc:
The entire document at https://api.npr.org/nprml is as follows:
https://api.npr.org/ 301 redirects to https://www.npr.org/api/index.