DATEX-II-EU / DatexII

Main repository for issues and bugs for the DATEXII standard

0 stars 0 forks source link

IMPORTED (34) - It should be possible to (de-)select enumeration literals when creating a subschema (Bugzilla Bug 232) #232

Closed datexii closed 5 years ago

datexii commented 5 years ago

This issue was created automatically with bugzilla2github.py

Bugzilla Bug 232

Date: 2019-03-01T11:50:33+01:00 From: @ingeniumfaber To: @jonas-jaderberg

Last updated: 2019-03-01T15:34:07+01:00

datexii commented 24 years ago

Comment 961

Date: 2000-01-01 01:01:01 +0100 From: @ingeniumfaber

I've had many complaints from users about excessive enumerations from which only very few literals were actually used by a service without being able to restrict the enumeration in the subschema generation process. The subschema significantly looses expressiveness without this feature and creates potential interoperability problems. I suggest that the tool alows deselecting unused literals in the schema generation process.

datexii commented 24 years ago

Comment 962

Date: 2000-01-01 01:01:01 +0100 From: bugzilla admin <webmaster@datex2.eu>

datexii commented 24 years ago

Comment 963

Date: 2000-01-01 01:01:01 +0100 From: @jonas-jaderberg

datexii commented 24 years ago

Comment 964

Date: 2000-01-01 01:01:01 +0100 From: @jonas-jaderberg

datexii commented 24 years ago

Comment 965

Date: 2000-01-01 01:01:01 +0100 From: @jonas-jaderberg

I have done some more thinking on this and I now agree with previous discussions between Josef and Bard on this topic, that this can be solved with documentation. To summarize my conclusion: If you make a sub schema and restricting enumerations there will be no problem on the server side because you still publish/send information that is a valid sub set of the whole schema. On the client side you can implement the whole schema or just the sub schema. As a general practice in web service development you should implement the schema/WSDL that the server that you are connecting too. So if you are connecting to another service with another sub schema with restricted enumerations you probably implement a new service that can talk to that service. This is also true if you like to use extensions. There is of course possible to implement the whole schema which can talk to any service that has a schema sub set.

datexii commented 5 years ago

Comment 966

Date: 2019-03-01 11:50:33 +0100 From: bugzilla admin <webmaster@datex2.eu>

--- Bug imported by webmaster@datex2.eu 2019-03-01 11:50 CET ---

This bug was previously known as bug 34 at https://bugzilla.datex2.eu/show_bug.cgi?id=34 This bug blocked bug(s) 2.

Unknown platform other. Setting to default platform "All". Missing Resolution. Setting status to UNCONFIRMED

datexii commented 5 years ago

Comment 1146

Date: 2019-03-01 13:04:14 +0100 From: bugzilla admin <webmaster@datex2.eu>

FIXED IN ISSUE TRACKER AFTER IMPORT

datexii commented 5 years ago

Comment 1280

Date: 2019-03-01 15:34:07 +0100 From: bugzilla admin <webmaster@datex2.eu>

fixed