AW: [dss-x] self-describing DSS-X instances

[Dr. Detlef Hühnlein <detlef.huehnlein@ecsec.de>]

Hi Andreas,

as a service may support different calls, profiles and options 
it would be good to have some standardised mechanism, 
which allows the server to announce its capabilities 
and on the other hand the client to discover the set of supported
features.

The "canonical way of informing the client" might be different 
for the different types of service technologies. Examples include
for 
1) REST:
	1.1) HATEOAS (https://en.wikipedia.org/wiki/HATEOAS) 
	1.2) WADL for REST-based services
	1.3) YAML-based OpenAPI (Swagger) specification 
2) WSDL for SOAP-based services 
3) yet another (probably XML-based) <Info> structure deposited at a well-known location.

While it might be good shift such recommendation to an annex or separate
document, we should IMHO address this somehow.

BR,
  Detlef




-----Ursprüngliche Nachricht-----
Von: dss-x@lists.oasis-open.org [mailto:dss-x@lists.oasis-open.org] Im Auftrag von Andreas Kuehne
Gesendet: Mittwoch, 24. Januar 2018 12:48
An: dss-x <dss-x@lists.oasis-open.org>
Betreff: [dss-x] self-describing DSS-X instances

Hi all,


the current version of the base schema includes a set of types to to self-decribe the DSS-X server instance (e.g. the DescriptionType). There are similiar concepts around, a popular one is HATEOS.

So I would consider to separate this topic from the DSS-X specification.
Like the TLS details included in core version 1.0 that outdated quickly the evolving area of instance meta information may render our specification effort useless.


What's your view on this?

Greetings,

Andreas

-- 

Andreas Kühne
phone: +49 177 293 24 97
mailto: kuehne@trustable.de

Trustable Ltd. Niederlassung Deutschland Gartenheimstr. 39C - 30659 Hannover Amtsgericht Hannover HRB 212612

Director Andreas Kühne

Company UK Company No: 5218868 Registered in England and Wales 



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php