Re: [dss-x] Regarding DSS core schema

[Stefan Drees <stefan@drees.name>]

Hi Andreas,

Am 16.01.13 19:32, schrieb Andreas Kuehne:
> ... finally found some time to go on working on our DSS conformance checker.
> Recently added a schema validator for requests and responses. A first
> surprising finding is that the 'Profile' attribute of the
> ResponseBaseType is 'required'. There was once a notice from Pim
> regarding this attribute that made it into the errata. But this comment
> underpins the 'required' state of the attribute. But I can see no reason
> why an implementor shouldn't just implement the core. Without any
> specific profile. So why should this attribute be 'required'?
> ...

thanks for adding the validator. I am curious, if I could somehow have a 
look at it or its sources ... :-?)

With respect to your finding:

In retrospect some differences between elements appear to be 
inconsistencies. We will have to look. Maybe there was a clever idea of 
one of the cooks involved when we prepared that meal in the years before 
2007 ;-)

I like to amend your question with the following:

As a ResponseBaseType[2] in dss version 1 makes sense, if and only if a 
RequestBaseType[1] has been instantiated, it looks a bit misaligned, 
that the client may optionally set a Profile attribute on the element 
based on RequestBaseType he is sending, but the server is required to 
set a Profile attribute inside the corresponding response element 
derived from ResponseBaseType.
Also since the type of the attribute in both cases is xs:anyURI the 
cardinality is fixed to one.
I sguugest, that we SHOULD investigate by digging through the mail 
archives and our minds what lead us there and how we SHOULD proceed.

References:


[1]: "2.10 Type <RequestBaseType>", 
http://docs.oasis-open.org/dss/v1.0/oasis-dss-core-spec-v1.0-os.html#_Toc157225013

[2]: "2.11 Type <ResponseBaseType>", 
http://docs.oasis-open.org/dss/v1.0/oasis-dss-core-spec-v1.0-os.html#_Toc157225014

All the best,
Stefan.