S
Simon Wright
I've been using a tool that objects to
<XMI xmlns:UML='org.omg.xmi.namespace.UML'
because
Invalid absolute IRI (Internationalized Resource Identifier) for
namespace: "org.omg.xmi.namespace.UML"
I know that most examples on the Web use URLs (eg http://...), but is
this IRI actually illegal?
I've checked RFC 3987 (http://www.rfc-editor.org/rfc/rfc3987.txt), and
I'm wondering whether the tool writer has misread the text specifying an
IRI-reference; this looks like an irelative-ref, which involves an
irelative-part, and the definition of irelative-part runs from the
bottom of Page 7 to the top of Page 8, which would allow an
ipath-noscheme ...
<XMI xmlns:UML='org.omg.xmi.namespace.UML'
because
Invalid absolute IRI (Internationalized Resource Identifier) for
namespace: "org.omg.xmi.namespace.UML"
I know that most examples on the Web use URLs (eg http://...), but is
this IRI actually illegal?
I've checked RFC 3987 (http://www.rfc-editor.org/rfc/rfc3987.txt), and
I'm wondering whether the tool writer has misread the text specifying an
IRI-reference; this looks like an irelative-ref, which involves an
irelative-part, and the definition of irelative-part runs from the
bottom of Page 7 to the top of Page 8, which would allow an
ipath-noscheme ...