Supplement 183: PS3.18 Web Services Re-Documentation
510Digital Imaging and Communications in Medicine (DICOM)Supplement 183: PS3.18 Web Services Re-Documentation1520DICOM Standards Committee, Working Group 27: Web Technologies1300 N. 17th Street Suite 1900Rosslyn, Virginia 22209 USAVERSION: Draft Letter BallotDeveloped in accordance with work item 2014-04-A.252016-06-03 10:11 AM1
2Supplement 183: PS3.18 Re-DocumentationVersion 55Editorial content – to be removed before Letter Ballot TextClosed Issues#1234567891011Closed IssuesCan any transaction or transactions with Query Parameters define new Query Parameters or new values for existingQuery Parameters?Decision: Yes. Any transaction may define new or extend existing Query Parameters. In addition, all origin serversshall ignore any parameters or values it does not support. See Section 8.3. This statement is made only once. It hasbeen removed from transactions that may have stated it.Should we define our own "reason phrases"?Decision: No, the Standard will not define new Reason Phrases, but an implementation is free to supply its ownreason phrases in responses.Should Section 7.7.6 on Caching Header Fields be included?Decision: Yes, it is informative for people not aware of them.For Query Parameters Names that the origin server doesn't recognize, should it just ignore them and their values?Decision: Yes, it should ignore both the Query Parameter name and its values and process the request as if theywere not there.For Query Parameters Values that the origin server does not recognize, should it just ignore them, or should it returnan error response? But what does invalid mean? Does it need to be defined for all Query Parameters.Decision: An origin server should ignore valid Query Parameter values it does not recognize and should process therequest as if the parameter were not present.Should the origin server be able to define and support additional Query Parameters or additional Query Parametervalues for an existing Query Parameter?Decision: Yes. If an origin server defines new or extends existing Query Parameters, they shall be included in theConformance Statement and, if the service supports it, the Retrieve Capabilities response.Should Conditional Requests and their Header Fields be included? See [RFC7232].Decision: No. If needed this can be done in a CP.Should all the applicable normative requirements in PS3.7 for the DIMSE services be replicated in this supplementas normative requirements for the RESTful Services. Our goal is to avoid asking people to read PS3.7.Decision: The requirements should be the same, unless the HTTP/S Standard requires a differenceShould we define a JSON canonical form to ensure interoperability.Decision: No, this should be done in a CP if needed.Defines terms: for the current terms service, transactionDo we define Web Services? No.Do we define 'DICOM Web Service' or 'DICOMweb Service'? ‘DICOM Web Service.Do we capitalize all http terms? No.What resources should the user agent have to support for the RS Retrieve transaction?Decision: User agent does not have support anything. We are not covering conformance statement in thissupplement.30CP NameStatus CodesSectionsX.Y.3.111.4.3.111.5.111.6.22Potential CPs after Supplement 183 is Final TextPotential CP Description200 with partial201 should be used whenever a new resource is created204 should be used for success without a payload.206 should only be used with Range Requests. Remove and replace with appropriatestatus code or define a Range request/response for search.409 is incorrect (which should be a conflict with the state of the resource). Not sure ofthe correct code. 412 or 422? Precondition failed (the precondition of it not alreadyexisting)? Elliot SilverAdd Cache-Control "no-cache"400 should be 412 or 422.Public Comment Draft
Supplement 183: PS3.18 Re-Documentation11.7.3.311.9.3.1Header Fields11.10.3.1all8.4Media list8.1111.211.11Status nex11.123If the target Workitem was already in the requested state, the response shall have a304 status and no payload.Remove status code 206 (206 should only be used with Range Requests) from Table11.9.3-1 and replace with 200?FixRemove 409 throughout except when real state conflicts might exist.Define origin server and user agent permissions and requirements with respect toheader fields.FixImprove specification of Selected Media Type and Selected Transfer SyntaxAdd Conditional Requests and their header fieldsAdd Range Requests and their header fieldsExplain how to establish a WebSocket. There are various methods.Allow Open WebSocket Connection to have a media type using the Accept/ContentType headers in the request/response.Add Close Notification ConnectionConsider doing a CP to improve Security and Privacy section.Why should a dashboard client be required to do creates and updates etc. And thevarious other cases described in UPS – KODDo we need a requirement to support the three transactions listed in 8.9 CommonRESTful transactions?Add ‘For a Worklist or a Filtered Worklist resource, the origin server will no longercreate new subscriptions to Workitems for the Subscriber and will no longer sendEvent Reports to the Subscriber related to any Workitems. This transactioncorresponds to the UPS DIMSE N-ACTION operation "Suspend Global Subscription".’Warning 299 - Isn’t that entirely included in a 409 response? What is the addedinformation here?Everywhere that you’ve indicated a specific warning message, etc. how should this behandled internationally? Are the messages always in ‘en-us’, or should they betranslated?Everywhere that you’ve indicated a specific warning message, etc. how should this behandled internationally? Are the messages always in ‘en-us’, or should they betranslated?Everywhere a specific warning message is indicated, how should this be handledinternationally? Are the messages always in ‘en-us’, or should they be translated?Fix warningsDescribe how Request UPS Cancel Action Information codes, etc. are encoded in thepayload.Look at code meaning in PS.3.3 or 3.4. Is that one atomic action, or two? Can anotherclient find the work item in InProgress?Update Table H-1 to include Non-Patient ObjectsCould write this as a profiling of the Send Event Report Transaction. "Shall implementthe Send Event Report Transaction with the following additional requirements." Orsome such KOD---- End of Editorial content – to be removed before Final Text----Scope and Field of Application of this SupplementThis supplement re-documents PS3.18 Web Services.35The goals of this re-documentation are:Public Comment Draft3
4Supplement 183: PS3.18 Re-Documentation 40 45Version 55Factor out text that is common to multiple services and in doing so 1) ensure uniformity and 2) make clearer and concisefor readers.Use a uniform format and style for documenting DICOM web services, making it easier to navigate and more efficient forreaders implementing multiple servicesBring the Standard into conformance with current Web Standards, especially [RFC7230 – 7234], and [RFC3986 – 3987].Use the Augmented Backus-Naur Form (ABNF) defined in [RFC5234] and [RFC7405] to specify the syntax of request andresponse messages.Use consistent terminology throughout the Standard.Use a consistent format for documenting services and transactions.The most important aspect of the re-documentation is that technical requirements of PS3.18 should not be changed. Errors,ambiguities, and underspecified aspects of the current PS3.18 have been corrected through the CP process prior to the finalizationof this supplement.4Public Comment Draft
Supplement 183: PS3.18 Re-Documentation5PS3.18Web ServicesPublic Comment Draft5
6Supplement 183: PS3.18 Re-DocumentationVersion 55PS3.18: DICOM PS3.18 2015c - Web ServicesCopyright6 2015Public Comment DraftNEMA
Supplement 183: PS3.18 Re-Documentation7Table of ContentsNotice and DisclaimerForeword 151Scope2Normative References3Definitions3.1DICOM Conformance3.2DICOM Information Object3.3DICOM Service Class Specifications3.4DICOM Data Structures and Encoding3.5DICOM Message Exchange3.6HyperText Transfer Protocol (HTTP/HTTPS)3.7DICOM Web Services4Symbols and Abbreviated Terms5Conventions5.1URIs versus URLs5.2Message Syntax5.2.1Common Syntactic Rules for Data Types5.2.2URI Templates5.2.3List Rule (‘#’)5.3Web Service Section Structure5.4Request and Response Header Field Tables6Conformance7Overview of DICOM Web Services (Informative)7.1DICOM Web Service Types7.1.1URI Web Service7.1.2RESTful Web Services and Resources7.2Resources, Representations, and Target URIs7.2.1DICOM RESTful Resources7.2.2Representations7.2.3Target URIs8Common Aspects of DICOM Web Services8.1Transactions8.1.1Request Message Syntax8.1.1.1Method8.1.1.2Target Resource8.1.1.3Query Parameters8.1.1.4Request Header Fields8.1.1.5Request Payload8.1.2Response Message Syntax8.1.2.1Status Codes8.1.2.2Response Header Fields8.1.2.3Response Payload8.2Target Resources8.3Query Parameters8.3.1Query Parameter Syntax8.3.1.1Query Parameter Syntax8.3.2Query Parameter Usage8.3.3Content Negotiation Query Parameters8.3.3.1Accept Query Parameter8.3.3.2Character Set Query Parameter8.3.4Search Query Parameters8.3.4.1Attribute Matching8.3.4.1.1Matching Rules8.3.4.2Fuzzy Matching of Person Names8.3.4.3Attributes Included in the Response8.3.4.4Response Pagination8.3.4.4.1Paging Behavior8.3.5Rendering Query Parameters8.3.5.1Query Parameters for Rendered Resources8.3.5.1.1Image Annotation8.3.5.1.2Image QualityPublic Comment 33334343535353536363637377
8Supplement 183: PS3.18 Re-Documentation8.3.5.1.3Viewport Scaling8.3.5.1.4Windowing8.3.5.2Query Parameters for Thumbnails8.4Header Fields8.4.1Content Negotiation Header Fields8.4.1.1Accept8.4.1.1.1Charset Media Type Parameter8.4.2Content Representation Header Fields8.4.3Payload Header Fields8.5Status Codes8.6Payloads8.6.1Payload Format8.6.1.1Single Part Payload8.6.1.2Multipart Payload8.6.1.2.1Multipart Payload Syntax8.6.2DICOM Representations8.6.2.1Composite SOP Instances8.6.2.2Web Service Constraints8.6.3Status Report8.7Media Types8.7.1Multipart Media Types8.7.2DICOM Resource Categories8.7.3DICOM Media Types8.7.3.1The application/dicom Media Type8.7.3.2DICOM Metadata Media Types8.7.3.3DICOM Bulkdata Media Types8.7.3.3.1Uncompressed Bulkdata8.7.3.3.2Compressed Bulkdata8.7.3.4DICOM Media Type Syntax8.7.3.4.1DICOM Multipart Media Types8.7.3.4.2Transfer Syntax Parameter8.7.3.4.3Character Set Parameter8.7.3.5Transfer Syntax Query Parameter8.7.3.6Acceptable Transfer Syntaxes8.7.3.7Support for DICOM Media Types by Service8.7.4Rendered Media Types8.7.5Acceptable Media Types8.7.6Accept Query Parameter8.7.7Accept Header Field8.7.8Selected Media Type and Transfer Syntax8.7.8.1Selected Media Type8.7.8.2Selected Transfer Syntax8.7.9Content-Type Header Field8.8Character Sets8.8.1Acceptable Character Sets8.8.2Character Set Query Parameter8.8.3Character Set Media Type Parameters8.8.4Accept-Charset Header Field8.8.5Selected Character Set8.9Retrieve Capabilities Transaction8.9.1Request8.9.1.1Resource8.9.1.2Query Parameters8.9.1.3Request Header Fields8.9.1.4Request Payload8.9.2Behavior8.9.3Response8.9.3.1Status Codes8.9.3.1.1Response Header Fields8.9.3.2Response Payload8.9.4Media Types8.10Notifications8.10.1 Overview8.10.2 Conformance8.10.3 Transaction Overview8.10.4 Open Notification Connection Transaction8.10.4.1 Request8Public Comment DraftVersion 606060616161616161616262626262626262
Supplement 183: PS3.18 Re-Documentation8.10.4.1.1 Target Resources8.10.4.1.2 Query Parameters8.10.4.1.3 Request Header Fields8.10.4.1.4 Request Payload8.10.4.2 Behavior8.10.4.3 Response8.10.4.3.1 CRLFStatus Codes8.10.4.3.2 Response Header Fields8.10.4.3.3 Response Payload8.10.5 Send Event Report Transaction8.10.5.1 Request8.10.5.1.1 Request Payload8.10.5.2 Behavior8.10.5.3 Response8.10.5.3.1 Response Payload8.11Security and Privacy9URI Web Service9.1Overview9.1.1Resource Descriptions9.1.2Common Query Parameters9.1.2.1Mandatory Query Parameters9.1.2.1.1Request Type9.1.2.1.2Study UID9.1.2.1.3Series UID9.1.2.1.4Instance UID9.1.2.2Optional Query Parameters9.1.2.2.1Acceptable Media Types9.1.2.2.2Acceptable Character Sets9.1.3Common Media Types9.2Conformance9.3Transactions Overview9.4Retrieve DICOM Instance Transaction9.4.1Request9.4.1.1Target Resource9.4.1.2Query .1.2.3Transfer Syntax9.4.1.3Request Header Fields9.4.1.4Request Payload9.4.2Behavior9.4.2.1Request Type9.4.2.2Study, Series, and Instance er Syntax UID9.4.3Response9.4.3.1Status Codes9.4.3.2Response Header Fields9.4.3.3Response Payload9.5Retrieve Rendered Instance Transaction9.5.1Request9.5.1.1Target Resource9.5.1.2Query Parameters9.5.1.2.1Frame Number9.5.1.2.2Image Annotation9.5.1.2.3Image Quality9.5.1.2.4Viewport9.5.1.2.4.1 Viewport Rows9.5.1.2.4.2 Viewport Columns9.5.1.2.5Source Image Region9.5.1.2.6Windowing9.5.1.2.6.1 Window Center9.5.1.2.6.2 Window Width9.5.1.2.7Presentation StatePublic Comment 6970707070707071717171717171727272729
10Supplement 183: PS3.18 Re-Documentation9.5.1.2.7.1 Presentation Series UID9.5.1.2.7.2 Presentation UID9.5.1.3Request Header Fields9.5.1.4Request Payload9.5.2Behavior9.5.2.1Frame Number9.5.2.2Viewport9.5.2.3Source Image Region9.5.2.4Windowing9.5.2.5Presentation State9.5.3Response9.5.3.1Status Codes9.5.3.2Response Header Fields9.5.3.3Response Payload10 Studies Service and Resources10.1Overview10.1.1 Resource Descriptions10.1.2 Common Query Parameters10.1.3 Common Media Types10.2Conformance10.3Transactions Overview10.4Retrieve Transaction10.4.1 Request10.4.1.1 Target Resources10.4.1.1.1 DICOM Resources10.4.1.1.2 Metadata Resources10.4.1.1.3 Rendered Resources10.4.1.1.4 Thumbnail Resources10.4.1.2 Query Parameters10.4.1.3 Request Header Fields10.4.1.4 Request Payload10.4.2 Behavior10.4.3 Response10.4.3.1 Status Codes10.4.3.2 Response Header Fields10.4.3.3 Response Payload10.4.4 Conformance Statement10.5Store Transaction10.5.1 Request10.5.1.1 Target Resources10.5.1.1.1 DICOM Resources10.5.1.2 Query Parameters10.5.1.3 Request Header Fields10.5.1.4 Request Payload10.5.2 Behavior10.5.3 Response10.5.3.1 Status Codes10.5.3.2 Response Header Fields10.5.3.3 Response Payload10.5.4 Media Types10.5.5 Conformance Statement10.6Search Transaction10.6.1 Request10.6.1.1 Target Resources10.6.1.2 Query Parameters10.6.1.2.1 Attribute / Value Pair Requirements10.6.1.2.2 Search Key Types and Requirements10.6.1.2.3 Required Matching Attributes10.6.1.3 Request Header Fields10.6.1.4 Request Payload10.6.2 Behavior10.6.3 Response10.6.3.1 Status Codes10.6.3.2 Response Header Fields10.6.3.3 Response Payload10.6.3.3.1 Study Resource10.6.3.3.2 Series Resources10Public Comment DraftVersion 868686868687878787888888898989898990
Supplement 183: PS3.18 Re-Documentation10.6.3.3.3 Instance Resources10.6.4 Media Types10.6.5 Conformance Statement11 Worklist Web Service and Resources11.1Overview11.1.1 Resource Description11.1.1.1 Workitems11.1.1.2 Workitem States and Transitions11.1.1.3 Deletion Locks and Workitem Lifetime11.1.1.4 Subscriptions and Notifications11.1.1.5 Web Services and DIMSE Terminology11.1.2 Common Query Parameters11.1.3 Common Media Types11.2Conformance11.3Transactions Overview11.4Create Workitem Transaction11.4.1 Request11.4.1.1 Target Resources11.4.1.2 Query Parameters11.4.1.3 Request Header Fields11.4.1.4 Request Payload11.4.2 Behavior11.4.3 Response11.4.3.1 Status Codes11.4.3.2 Response Header Fields11.4.3.3 Response Payload11.5Retrieve Workitem Transaction11.5.1 Request11.5.1.1 Target Resources11.5.1.2 Query Parameters11.5.1.3 Request Header Fields11.5.1.4 Request Payload11.5.2 Behavior11.5.3 Response11.5.3.1 Status Codes11.5.3.2 Response Header Fields11.5.3.3 Response Payload11.6Update Workitem Transaction11.6.1 Request11.6.1.1 Target Resources11.6.1.2 Query Parameters11.6.1.3 Request Header Fields11.6.1.4 Request Payload11.6.2 Behavior11.6.3 Response11.6.3.1 Status Codes11.6.3.2 Response Header Fields11.6.3.3 Response Payload11.7Change Workitem State11.7.1 Request11.7.1.1 Target Resources11.7.1.2 Query Parameters11.7.1.3 Request Header Fields11.7.1.4 Request Payload11.7.2 Behavior11.7.3 Response11.7.3.1 Status Codes11.7.3.2 Response Header Fields11.7.3.3 Response Payload11.8Request Cancellation11.8.1 Request11.8.1.1 Target Resources11.8.1.2 Query Parameters11.8.1.3 Request Header Fields11.8.1.4 Request PayloadPublic Comment 510510510510510610611
12Supplement 183: PS3.18 Re-Documentation11.8.2 Behavior11.8.3 Response11.8.3.1 Status Codes11.8.3.2 Response Header Fields11.8.3.3 Response Payload11.9Search Transaction11.9.1 Request11.9.1.1 Target Resources11.9.1.2 Query Parameters11.9.1.3 Request Header Fields11.9.1.4 Request Payload11.9.2 Behavior11.9.3 Response11.9.3.1 Status Codes11.9.3.2 Response Header Fields11.9.3.3 Response Payload11.10 Subscribe Transaction11.10.1 Request11.10.1.1 Target Resources11.10.1.2 Query Parameters11.10.1.3 Request Header Fields11.10.1.4 Request Payload11.10.2 Behavior11.10.3 Response11.10.3.1 Status Codes11.10.3.2 Response Header Fields11.10.3.3 Response Payload11.11 Unsubscribe Transaction11.11.1 Request11.11.1.1 Target Resources11.11.1.2 Query Parameters11.11.1.3 Request Header Fields11.11.1.4 Request Payload11.11.2 Behavior11.11.3 Response11.11.3.1 Status Codes11.11.3.2 Response Header Fields11.11.3.3 Response Payload11.12 Workitem Event Reports12 Non-Patient Instance Web Service and Resources12.1Overview12.1.1 Resource Descriptions12.1.2 Common Query Parameters12.1.3 Common Media Types12.2Conformance12.3Transactions Overview12.4Retrieve Transaction12.4.1 Request12.4.1.1 Target Resources12.4.1.2 Query Parameters12.4.1.3 Request Header Fields12.4.1.4 Request Payload12.4.2 Behavior12.4.3 Response12.4.3.1 Status Codes12.4.3.2 Response Header Fields12.4.3.3 Response Payload12.5Store Transaction12.5.1 Request12.5.1.1 Target Resources12.5.1.2 Query Parameters12.5.1.3 Request Header Fields12.5.1.4 Request Payload12.5.2 Behavior12.5.3 Response12.5.3.1 Status Codes12.5.3.2 Response Header Fields12Public Comment DraftVersion 119
Supplement 183: PS3.18 Re-Documentation12.5.3.3 Response Payload12.6Search Transaction12.6.1 Request12.6.1.1 Target Resources12.6.1.2 Query Parameters12.6.1.3 Request Header Fields12.6.1.4 Request Payload12.6.2 Behavior12.6.3 Response12.6.3.1 Status Codes12.6.3.2 Response Header Fields12.6.3.3 Response PayloadAnnex A Collected ABNFAnnex B Examples (Informative)Annex C Applications (Informative) (Retired)Annex D IANA Character Set MappingsAnnex E WADO-WS Schemas and Examples (Retired)Annex F DICOM JSON ModelAnnex H Capabilities DescriptionAnnex G WADL JSON RepresentationPublic Comment 2312412512613713913
14Supplement 183: PS3.18 Re-Documentation2016-02-19Notice and DisclaimerThe information in this publication was considered technically sound by the consensus of persons engaged in the development andapproval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreementamong every person participating in the development of this document.NEMA standards and guideline publications, of which the document contained herein is one, are developed through a voluntaryconsensus standards development process. This process brings together volunteers and/or seeks out the views of persons whohave an interest in the topic covered by this publication. While NEMA administers the process and establishes rules to promotefairness in the development of consensus, it does not write the document and it does not independently test, evaluate, or verify theaccuracy or completeness of any information or the soundness of any judgments contained in its standards and guidelinepublications.NEMA disclaims liability for any personal injury, property, or other damages of any nature whatsoever, whether special, indirect,consequential, or compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on thisdocument. NEMA disclaims and makes no guaranty or warranty, expressed or implied, as to the accuracy or completeness of anyinformation published herein, and disclaims and makes no warranty that the information in this document will fulfill any of yourpurposes or needs. NEMA does not undertake to guarantee the performance of any individual manufacturer or seller's products orservices by this Standard or guide.In publishing and making this document available, NEMA is not undertaking to render professional or other services for or onbehalf of any person or entity, nor is NEMA undertaking to perform any duty owed by any person or entity to someone else.Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of acompetent professional in determining the exercise of reasonable care in any given circumstances. Information and otherstandards on the topic covered by this publication may be available from other sources, which the user may wish to consult foradditional views or information not covered by this publication.NEMA has no power, nor does it undertake to police or enforce compliance with the contents of this document. NEMA does notcertify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement ofcompliance with any health or safety-related information in this document shall not be attributable to NEMA and is solely theresponsibility of the certifier or maker of the statement.14Public Comment Draft
Supplement 183: PS3.18 Re-Documentation15ForewordThis DICOM Standard was developed according to the procedures of the DICOM Standards Committee.The DICOM Standard is structured as a multi-part document using the guidelines established in [ISO/IEC Directives, Part 3].PS3.1 should be used as the base reference for the current Parts of this Standard.Public Comment Draft15
161Supplement 183: PS3.18 Re-DocumentationScopePS3.18 specifies web services (using the HTTP family of protocols) for managing and distributing DICOM (Digital Imaging andCommunications in Medicine) Information Objects, such as medical images, annotations, reports, etc. to healthcare organizations,providers, and patients. The term DICOMweb is used to designate the RESTful Web Services described here.Security considerations, including access control, authorization, and auditing are beyond the scope of PS3.18. Refer to PS3.15Security and System Management Profiles.16Public Comment Draft
Supplement 183: PS3.18 Re-Documentation217Normative ReferencesThe following normative documents contain provisions that, through reference in this text, constitute provisions of this part ofDICOM. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However,parties to agreements based on this part of DICOM are encouraged to investigate the possibility of applying the most recenteditions of the normative documents indicated below. For undated references, the latest edition of the normative document referredto applies. Members of ISO, IEC, and IETF maintain registries of currently valid International Standards.HL7 CDAHealth Level Seven, Clinical Document Architecture (CDA)IEC 61966-2.1IEC. 1999. Multimedia systems and equipment - colour measurement andmanagement - Part 2.1: colour management - Default RGB colour space –sRGB. ISBN: 2-8318-4989-6 - ICS codes: 33.160.60, 37.080 - TC 100 - 51 pp.as amended by Amendment A1:2003.https://en.wikipedia.org/wiki/RGB color spaceIETF RFC822Standard for ARPA Internet Text Messages http://tools.ietf.org/html/rfc822IETF RFC2045and followings MIME Multipurpose Internet Mail Extensionhttp://tools.ietf.org/html/rfc2045IETF RFC2046Multipurpose Internet Mail Extensions (MIME) Part Two: Media Typeshttps://tools.ietf.org/html/rfc2046IETF RFC2387The MIME Multipart/Related Content-type https://tools.ietf.org/html/rfc2387IETF RFC2978IANA Charset Registration Procedures https://tools.ietf.org/html/rfc2978IETF RFC3240Application/dicom MIME Subtype Registration http://tools.ietf.org/html/rfc3240IETF RFC3536Terminology Used in Internationalization in the 3IETF RFC3986Uniform Resource Identifiers (URI): Generic Syntaxhttp://tools.ietf.org/html/rfc3986IETF RFC4648The Base16, Base32, and Base64 Data Encodings.https://tools.ietf.org/html/rfc4648IETF RFC5234Augmented BNF for Syntax Specifications: ABNFhttp://tools.ietf.org/html/rfc5234IETF RFC6338Media Type Specifications and Registration https://tools.ietf.org/html/rfc6838IETF RFC6365Terminology Used in Internationalization in the IETFhttps://tools.ietf.org/html/rfc6365IETF RFC6455The WebSocket Protocol http://tools.ietf.org/html/rfc6455IETF RFC6365Terminology Used in Internationalization in the IETFhttps://tools.ietf.org/html/rfc6365IETF RFC6570URI Template http://tools.ietf.org/html/rfc6570IETF RFC6838Media Type Specifications and Registration Procedures https://tools.ietf.org/html/rfc6838 IETF RFC7159The JavaScript Object Notation (JSON) Data Interchange Format.https://tools.ietf.org/html/rfc7159IETF RFC7230Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routinghttp://tools.ietf.org/html/rfc7230IETF RFC7231Hypertext Transfer Protocol (HTTP/1.1): Semantics and Contenthttp://tools.ietf.org/html/rfc7231IETF RFC7232Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsPublic Comment Draft17
18Supplement 183: PS3.18 IETF RFC7233Hypertext Transfer Protocol (HTTP/1.1): Range Requestshttp://tools.ietf.org/html/rfc7233IETF RFC7234Hypertext Transfer Protocol (HTTP/1.1): Caching http://tools.ietf.org/html/rfc7234IETF RFC7235Hypertext Transfer Protocol (HTTP/1.1): TF RFC7236Initial Hypertext Transfer Protocol (HTTP) Authentication Scheme F RFC7237Initial Hypertext Transfer Protocol (HTTP) Method F RFC7303XML Media TypeIETF-RFC7405Case-Sensitive String Support in ABNF https://tools.ietf.org/html/rfc7405IHE ITI TF-2x:Appendix VIHE IT Infrastructure Technical Framework, Volume 2x, Appendix V (WebServices for IHE Transactions)ISO/IEC Directives, Part 3 ISO/IEC. 1989. Drafting and presentation of International Standards.ISO/IEC 10918JPEG Standard for digital compression and encoding of continuous-tone stillimagesISO/IEC 2022:1994Information technology -- Character code structure and tions/standards/Ecma-035.htmSUBM-wadl20090831Web Application Description Language (WADL), W3C Member Submission 31August 2009 http://www.w3.org/Submission/wadl/)18Public Comment Draft
Supplement 183: PS3.18 Re-Documentation319DefinitionsFor the purposes of this part of DICOM, the following terms and definitions apply.3.1DICOM ConformancePS3.18 makes use of the following terms defined in PS3.2:5Conformance Statement3.2DICOM Information ObjectThis PS3.18 makes use of the following terms defined in PS3.3:Multi-frame image3.310DICOM Service Class SpecificationsThis PS3.18 makes use of the following terms defined in PS3.4:Real-World ActivityService-Object Pair (SOP) ClassService-Object Pair (SOP) Instance3.415DICOM Data Structures and EncodingPS3.18 makes use of the following terms defined in PS3.5:Data ElementData Element TagUnique Identifier (UID)3.520DICOM Message ExchangePS3.18 makes use of the following terms defined in PS3.7:DICOM Message Service Element (DIMSE)3.6HyperText Transfer Protocol (HTTP/HTTPS)PS3.18 makes use of the following terms defined in IETF RFC 7230 Section 2.1 Client/Server Messaging:HTTP25HTTPSorigin serveruser agent3.7DICOM Web ServicesPS3.18 defines the following terms.30BulkdataAn object that contains an octet-stream containing one or more Value Fields (typically containing large data, such as PixelData) extracted from a DICOM Dataset. See Metadata.Notes1.The octet-stream does not include the Attribute Tag, Value Representation, or Attribute Length.Public Comment Draft19
20Supplement 183: PS3.18 Re-Documentation352.For the value of a frame of a Pixel Data attribute encoded in a compressed Transfer Syntax, it does not includethe Basic Offset Table and Data Stream Fragment Item tags and lengths.Bulkdata URIA Uniform Resource Identifier that references Bulkdata.DICOM Object40An instance of a data object as defined by PS3.3 that has been allocated an unique identifier in the format specified forSOP Instance UID in PS3.3 and has been chosen as an object to be saved securely for some period of time. Within theDICOM Standard, a DICOM Object is typically a Composite Service Object Pair (SOP) Instance.DICOM ResourceOne or more DICOM Objects that are referenced by a URI.45Event ReportA Dataset containing elements describing an event that occurred on the origin server. See Section 11.12.MetadataA DICOM Dataset where zero or more elements (typically containing large data, such as Pixel Data) have been replacedwith Bulkdata URIs.50DIMSE ProxyAn origin server that responds
3.1 DICOM Conformance 19 3.2 DICOM Information Object 19 3.3 DICOM Service Class Specifications 19 3.4 DICOM Data Structures and Encoding 19 3.5 DICOM Message Exchange 19 3.6 HyperText Transfer Protocol (HTTP/HTTPS) 19 3.7 DICOM Web Services 19 4 Symbols and Abbr
19 FALLOUT: NEW VEGAS 360, PS3 Mature 20 FINAL FANTASY XIII 360, PS3 Teen 1 CALL OF DUTY: BLACK OPS 360, PS3, Wii, NDS Mature 2 MADDEN NFL 11 360, PS3, Wii, PS2, PSP Everyone 3 HALO: REACH 360 Mature 4 NEW SUPER MARIO BROS. WII Wii Everyone 5 RED DEAD REDEMPTION 360, PS3 Mature 6 WII FIT PLUS Wii Everyone
PS3 Pressure Switch Technical Data PS3_35003_EN_R06.doc 1 / 10 04.04.2006 The ALCO PS3 is a Pressure Switch with fixed switch-point settings. Features Maximum Operating Pressure up to 43 bar . High Pressure Controls PS3-A6S 0 715 603 16,0 11,0 7/16"-20 UNF PS3-A6S 0 715 604 19,0 15,0 Auto 70 C 150C 48 female thread with .
182 IUPUI All-Campus Bulletin 2004-06 183 Administration of Graduate Programs at IUPUI 183 IUPUI Graduate Office 183 IUPUI Graduate Affairs Committee 183 Integrity in Graduate Education 183 General Graduate School Regulations and Information 183 English as a Second Language (ESL) Placement Test 184 English Proficiency 184 GRE (Graduate Record .
8. Congrats, you now have SACD ripping capability installed on your PS3! Section 4 - Using SACD-ripper on your PS3 1. You are now ready to rip your first SACD! 2. Navigate to the "Games" section of your PS3 3. Select "Unknown" 4. Select " SA D-Ripper" (UPDATE choose "yes" and go to Section 4A if you have a PS3 connected
4 4-PS3-1.Use evidence to construct an explanation relating the speed of an object to the energy of that object. -PS3 2. Make observations to provide evidence that energy can be transferred from place to place by sound, light, heat, and electric currents. 4-PS3-3. Ask questions and predict outcomes about the changes in energy that occur when
Physical Science 3 (PS3) PS3 Move SE 2.0.5 ISBN-13: 978-1-937846-12-1. Physical Science 3 (PS3) How Will It Move? Force and Motion . following people and institutions for the images in this book. Lesson 1 Atlanta Surface Area Map – Courtesy WSI Corporation, The Weather Channel Belem Sur
Rodric Rabbah, IBM ESWeek3 2007 Salzburg, Austria PS3 Cell Processor Cell Broadband Engine Architecture Heterogeneous multicore architecture with 9 cores 1 general purpose core: Power Processor Element (PPE) 8 accelerator cores: Synergistic Processor Elements (SPEs) On the PS3 only 6 SPEs
no longer recognized on PS3 , PS4 , PS5 or PC (i.e. in the event of firmware loss) FRANÇAIS- METHODE BOOTLOADER : Procédure pour réveiller votre volant s’il n’est plus du tout reconnu sous PS3 , PS4 , PS5 ou sur PC (en cas de perte de firmware
