The Synthax that is required to encode an URI is very general. There is fixed encoding according to US-ASCII standards
There is also a standard that revers to the referees to the Universal Character Code (Unicode/ISO 10646) where it is possible to also use international symbols., i.e. symbols that are not in the US-ASCII encoding.
Percent Encoding for reserved characters, or characters that do not exist in US-ASCII encoding and there are reserved characters that have special functions and permitted characters as well as not-permitted characters.
pct-endoced = "%" HEDIG HEXDIG
Reserved characters with special function
unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
Extension to Universal Character Code (Unicode/ISO 10646)
The schema for an URI is very simple. It starts with a schema that describes the primary access mechanisms and the protocol that is used to receive or to get the address / the name. Then there are mandatory/optional parts, e.g. the information about username and password, the information about port numbers to use or a pathname or a query string, or a fragment identifier. Mandatory or essential is the access schema, then there is a separator. After the separator there is the host name. After the host name there might come access path and maybe also the filename of the document that has to be retrieved from the files server. After the filename additional parameters an be transfered and communicated via a query or specifying a special part of the document.
URI = schema"://"[userinfo@"]host[:port][path]["?"query]["#"fragment]
Therefore and URI consists of:
Exception Multimedia Fragments Multimedia-Resources have time (temporale) and location (spatial) dimension dead-on Access via URI Fragment Identifier * Consequences for manegment of clinet and Server, i.e. Changes in http-Protocol are also required