OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss-x message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dss-x] Re: [dss-comment] Defining URIs ?


Dear Andreas,

Dear Andreas,

Just a couple of comments: the core already identifies some values for ResultMinor (you may see the values searching for "ResultMinor", as it does the profile for multisignature validaton reporting. Having said that I tend to concur with you that they could define new URIs for ResultMinor as long as **they do not break** the rules specified in the core. I am saying this because in clause 2.6 the core states:
"One of the following <ResultMinor> values MUST be returned when the <ResultMajor> code is Success."

Consequently, I would say that at the moment the set of URIs for ResultMinor in the case of success is fully restricted. As they speak of errors, would say that they are not affected by this requirement. For the other case the core says:

"The following <ResultMinor> values is suggest MAY be returned when the <ResultMajor> code is RequesterError."


And by the way, I would say that we have an issue here: would say that "is suggest" should be dropped. Additionaly some text should be added making it clear two things
1. that other URIs may appear
2. Specify that under these circumpstances the server will make it clear the semantics of each specific URI, as the core does with the listed URIs

So, I think that we have another issue to the list of issues of the core.

As for the sample requests, I think that there are some of them in the wiki from the old times when we run some interoperability....

Regards

Juan Carlos.

El 26/7/16 a las 17:20, Andreas Kuehne escribió:
Hi folks,

I would suppose to answer that special ResultMinors are no problem as
long as the success / error conditions are not already covered by the
core. The schema does not reject any new ResultMinor URIs.

Any objections?

Regarding the sample requests I would like to point him to Juan Carlos
set of files.

Greetings,

Andreas
Dear all,



I’m currently working with Oasis DSS and I have a few questions.

I’m using an already existing signing server and we want it to be compliant
with Oasis DSS. The problem is that the set of errors returned by this
server is very specific and does not match with those defined by the Core
or the profiles.



So, I’d like to know what are exactly the possibilities for me to work with
DSS because the URIs defined aren’t detailed enough. I know we can’t define
URIs for ResultMajor because URIs MUST be values defined by this
specification or by some profile of this specification, but what about
ResultMinor or DetailType ?

Should we define our own URIs to be used with ResultMinor ? If yes, what
are the restrictions to do so ? What are you recommending ?



Furthermore, is there any set of request/response that could be used as
examples/tests ?



Thank you in advance,



Regards,

Sebastien





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]