It's unclear that primitive type "uri" enclose URNs (not only URLs) #126
Milestone
Comments
I suggest to rename |
Jhuni0123
added a commit
to Jhuni0123/nirum
that referenced
this issue
May 21, 2018
Jhuni0123
added a commit
to Jhuni0123/nirum
that referenced
this issue
May 21, 2018
Jhuni0123
added a commit
to Jhuni0123/nirum
that referenced
this issue
May 21, 2018
Jhuni0123
added a commit
to Jhuni0123/nirum
that referenced
this issue
May 21, 2018
The compiler 0.4 will be released with a new type name In the next minor release we need to obsolete |
PR #281 implemented it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, Nirum specification doesn't clarify their implementors to treat "uri" be a union of Uniform Resource Locator and Uniform Resource Name, or accept URL only and reject URN. Because URN is used rarely in practice, most of Nirum users might want to exclude URN during serialization and deserialization. Furthermore, most of programming languages don't have URN datatype in their standard library. It makes hard to implement the runtime for them.
The text was updated successfully, but these errors were encountered: