Spring til login

RSS-feeds

Søgning

OIO Reliable Asynchronous Secure Profile Version 1.2

Type: Teknisk specifikation
Version: 1.2 - Publiceret: 27.08.2009
Ansvarlig: Brian Nielsen

Changes:

In response to the feedback from the public hearing the OIO Reliable Asynchronous Secure Profile has been updated:

  • The HTTP protocol has been made primary whereas SMTP is secundary and optional for profile compliance
  • ReceiverPartyIdentifierType and SenderPartyIdentifierType has become optional in the XML Schema for the RASP custom header to reflect the "SHOULD".
  • Versionen has been updated to 1.2
  • DNITA vil later provide a document on how to provide "digital evidence"

About:

Reliable Asynchronous Secure Profile (OIO RASP) is a profile of web service standards from the WS-* family of standards. It supports asynchronous exchange of business documents via the Internet with a high degree of security and reliability in the transactions.

This document defines the OIO Reliable Asynchronous Secure Profile 1.2, consisting of a set of non-proprietary Web services specifications, along with clarifications, refinements, interpretations and amplifications of those specifications which promote interoperability.

Open process

OIO RASP has been developed in an open and accountable process at the Danish National IT and Telecom Agency. Input has been given from several public sector institutions as well as private companies through workshops and public hearings.

Resources

and closely related

The OIO Service Metadata Interface is not part of the RASP profile but is composable with RASP.

 

Artefakter

Filer og referencer
Titel Type
OIO_Reliable_Asynchronous_Secure_Profile_1.2.pdf pdf Download Vis supplerende information ...

Klassifikationer

Supplerende information

Indlæg til ressource

Profilens billede

Regarding custom SOAP headers to be used with OIO RASP

Brian Nielsen - 27.05.2010

Hi Arvinder Singh

Thank you for giving us feedback. I see you point and it's my understanding that the current plan for with the next release for NemHandel is that these custom SOAP headers will become mandatory. 

That said, the target audience for OIORASP is broader than NemHandel and I could image usage scenarios outside the context of NemHandel where these headers would not be required, but there has not been any decisions on this yet.

Best regards

Brian Nielsen 

Profilens billede

ReceiverPartyIdentifierType and SenderPartyIdentifierType as optional

Arvinder Singh - 13.05.2010

Well we have been living with this "mishap", so this comment is more of a reflection.

Why are these type fields optional ? without them the identifier is meaningless, unless (as the RASP reference implementation has done it) to assume that an identifier is of some type based on length.

Requiring the types being mandatory would make the implementaion simpler and more general.

Ønsker du at skrive indlæg eller blot kommentere indlæg,
skal du være oprettet som bruger og logget ind.

Opret dig som Ny bruger    Log ind     eller

Tilføj fil(er)

En ny fil vil overskrive en eksisterende fil, hvis begge filer har samme navn og samme ekstension.

Profil - Log ind

Minimér boks

Tags

Tilføj dine egne tags

- (kræver login)

Andre brugeres tags til ressourcen

Der er ikke tilknyttet tags fra andre brugere

Minimér boks
Versioner
Version Dato
1.2 (valgte) 27.08.2009 Vis supplerende information ...
1.2 16.04.2009 Vis supplerende information ...
1.0 20.03.2009 Vis supplerende information ...