XDS.a Implementation Notes: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Kevino (talk | contribs)
No edit summary
Kevino (talk | contribs)
 
Line 3: Line 3:
=== Generating a URI ===
=== Generating a URI ===
When generating a URI to put into the metadata element XDSDocumentEntry.URI, the implementer must remember to properly encode it.  This is especially important when using the attribute XDSDocumentEntry.uniqueId in the URI string.  This attribute can include the '^' character which is not legal in a URI.  It must be escaped as %5E.
When generating a URI to put into the metadata element XDSDocumentEntry.URI, the implementer must remember to properly encode it.  This is especially important when using the attribute XDSDocumentEntry.uniqueId in the URI string.  This attribute can include the '^' character which is not legal in a URI.  It must be escaped as %5E.
== See Also ==
The [[IT Infrastructure]] Domain manages this profile.
The [http://www.ihe.net/Technical_Framework/index.cfm#IT ITI Technical Framework] is the official master document for this Profile.
The [[Cross Enterprise Document Sharing]] page is an overview of the Profile.


[[Category:Profile Implementations]]
[[Category:Profile Implementations]]

Latest revision as of 23:19, 9 December 2008

ITI-15 Provide and Register Document Set

Generating a URI

When generating a URI to put into the metadata element XDSDocumentEntry.URI, the implementer must remember to properly encode it. This is especially important when using the attribute XDSDocumentEntry.uniqueId in the URI string. This attribute can include the '^' character which is not legal in a URI. It must be escaped as %5E.

See Also

The IT Infrastructure Domain manages this profile.

The ITI Technical Framework is the official master document for this Profile.

The Cross Enterprise Document Sharing page is an overview of the Profile.