Open divergentdave opened 1 year ago
If/when this draft is adopted, I think we could make a case for extending the namespace. (i.e., say "extensions to DAP MAY extend the namespace"). In the meantime, I believe you're right.
@divergentdave @cjpatton please suggest what should I do to fix this. Am I right it blocked by DAP section 8.3?
Let's hold this issue open until we get to WG call-for-adoption. If we discuss this at IETF 118, then I suggest bringing up the issue then.
The document currently suggests that the type
urn:ietf:params:ppm:dap:error:invalidTask
should be used in problem details responses. However, DAP says "Servers MUST NOT use the DAP URN namespace for errors not listed in the appropriate IANA registry". Thus, the taskprov document's 'IANA Considerations' section should either add aninvalidTask
entry to the contents of DAP's URN registry, or create a separate namespace of its own.