Uniform Resource Identifiers (URI's)
Introduction
- bitcoin
- geo
- im
- irc
- ircs
- magnet
- mailto
- mms
- news
- nntp
- openpgp4fpr
- sip
- sms
- smsto
- ssh
- tel
- urn
- webcal
- wtai
- xmpp
URI Resolvers
{ /cgi-bin/uri-res/
,
/uri-res/
}
tag:
URI Scheme
tag:
URI Syntax Diagram.
{ Generally, when the
authorityInfo
as a user email address belongs to the
owner of the email address }
{ Although RFC 4151 states that tag:
URIs are distinct
from most other URIs
in that they have no authoritative resolution mechanism, and may be
used purely as an entity identifier
[citation needed], MT Invictus' URI resolvers will, if possible,
resolve a tag under its domain. }
accounting@example.org
tags
{ These tags are exclusively used to tag accounting basis documents. }
tag:accounting@example.org,YYYY-MM-DD:nnn…
{ Where YYYY, MM, DD and nnn }
asset@example.org
and
asset@example.net
tags
{ These tags are exclusively used to tag organization assets. }
tag:asset@example.org,YYYY-MM-DD:nnn…
{ Where YYYY, MM, DD and nnn }
invoice@example.org
tags
tag:invoice@example.org,YYYY:nnn…18CC
order@example.org
tags
tag:order@example.org,YYYY:nnn…24CC
urn:
URI Scheme
NID's include:
etsi:
— European Telecommunications Standards Instituteiana:
— Internet Assigned Numbers Agencyietf:
— Internet Engineering Task Forceisbn:
— International Standard Book Numbersissn:
— International Standard Serial Numbersiso:
— International Standards Organizationitu:
— International Telecommunications Unionnbn:
— National Book Numbers
web+*:
URI Schemes
web+
schemes start with the four characters
“web+
” and are followed by one or more
letters in the range a-z. It effectively namespaces web-based
protocols from other, potentially less web-secure, protocols. Any Web
page is able to register a handler for all
“web+
” schemes. As such, these schemes must
not be used for features intended to be core platform features (e.g.
network transfer protocols like HTTP or FTP). Similarly, such schemes must not
store confidential information in their URLs, such as usernames,
passwords, personal information, or confidential project names.
This convention is not associated with the registration of any new scheme but is currently a requirement as well as convention for non-whitelisted web-based protocols.
web+barcode:
URI Scheme
web+barcode:/format/data[?hint=clue]
Query Strings
Prefixes
ix
— Input
ox
— Output
a
— Generic Action
e
— Generic Encoding
f
— Generic Format
{ A media type (formerly known as MIME type) is a two-part identifier for file formats and format contents transmitted on the Internet. The Internet Assigned Numbers Authority (IANA) is the official authority for the standardization and publication of these classifications. It has the following format: }
type/subtype
If subtype
is unique,
type can be omitted.
l
— Generic Language
n
— Generic Count
{ In mathematics, the italic form n is a particularly common symbol for a variable quantity which represents a natural number. In statistics, it represents the sample size. }
q
— Generic Query
sz
— Generic Size
ts
— Generic Timestamp
{ A common use of the
ts
field is to make an URL unique to prevent caching.
}
MT Invictus web apps should as far as possible not throw errors
or warnings if they encounter ts
fields in requests and
they don't use it.
u
— Generic URL
Suffixes
Object Notation
{ Use dot notation whenever possible for objects, bracket notation for arrays, and numeric indices for the latter. }
{ If empty brackets occur at the end of a variable name, ///. If they occur in the middle, /// }
References and Further Reading
- Uniform Resource Identifier (URI) Schemes. Internet Assigned Numbers Agency (IANA). Date retrieved .
- Uniform Resource Name (URN) Namespaces. Internet Assigned Numbers Agency (IANA). Date retrieved .
- Contributors of Wikipedia: List of URI Schemes. Wikipedia — The Free Encyclopedia. Last Modified: . Date Retrieved: .
- Media Types. Internet Assigned Numbers Agency (IANA). Date retrieved .
- Contributors of Wikipedia: Media type. Wikipedia — The Free Encyclopedia. Last Modified: . Date Retrieved: .
- Ron Daniel: A Trivial Convention for using HTTP in URN Resolution. IETF RFC 2169. Internet Engineering Task Force (IETF), .
- Karen Sollins: Architectural Principles of Uniform Resource Name Resolution. IETF RFC 2276. Internet Engineering Task Force (IETF), . Updated by RFCs 3401, 3402, 3403, 3404, and 3405.
- Michael Mealling: Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS. IETF RFC 3401. Internet Engineering Task Force (IETF), .
- Michael Mealling: Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm. IETF RFC 3402. Internet Engineering Task Force (IETF), .
- Michael Mealling: Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database . IETF RFC 3403. Internet Engineering Task Force (IETF), .
- Michael Mealling: Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) Resolution Application. IETF RFC 3404. Internet Engineering Task Force (IETF), .
- Michael Mealling: Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures. IETF RFC 3405, BCP 65. Internet Engineering Task Force (IETF), .
- Tim Kindberg, Sandro Hawke: The 'tag' URI Scheme. IETF RFC 4151. Internet Engineering Task Force (IETF), .