Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

categories / utilities #6

Closed
sunilkale74 opened this issue Apr 18, 2017 · 4 comments
Closed

categories / utilities #6

sunilkale74 opened this issue Apr 18, 2017 · 4 comments
Labels
Feature Request Missing functionality and changes
Milestone

Comments

@sunilkale74
Copy link

Hi Jens,

Eine Frage zu der Nutzung/Kategorisierung (XSD). Haben wir hier (siehe Abschnitt XSD unten) die Möglichkeit vorgesehen mehrere Nutzungsarten (utilities) pro Objekt sowie mehrere Kategorien (categories) zuzulassen und wie kommt ihr auf maximal drei (maxOccurs=3)?

Danke und Gruss,
Sunil

                <xs:element name="categories" minOccurs="0" maxOccurs="1">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element type="categoryTypes" name="category" minOccurs="1" maxOccurs="3"/>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>

                <xs:element name="utilities" minOccurs="0" maxOccurs="1">
                  <xs:complexType>
                    <xs:sequence>
                      <xs:element type="utilityTypes" name="utility" minOccurs="1" maxOccurs="3"/>
                    </xs:sequence>
                  </xs:complexType>
                </xs:element>
@jensberndt
Copy link
Collaborator

jensberndt commented Apr 18, 2017 via email

@jaggli jaggli added Feature Request Missing functionality and changes Status: Backlog labels Oct 30, 2018
@jaggli
Copy link
Contributor

jaggli commented Nov 28, 2018

We already removed the 0..3 occurence for categories, in #46 - so the first question is answered.
@jensstalder any objections when we remove theutilization limitation of 3 as well? (this is what utilityTypes are called now)

@jaggli jaggli added this to the 1.0.0 milestone Nov 28, 2018
@jaggli jaggli added the Needs clarification Blocked - additional information required. label Nov 28, 2018
@jensstalder
Copy link
Collaborator

There should be no such restriction. Was probably added due to some sort of "fear" during the first draft. Consumers can decide to, for example, only consider the first 3. The order is important however, aka the first one stated is the one the sender wants, if that does'nt work go to 2 then 3 etc. I can't see that restricting this would help.

@jaggli
Copy link
Contributor

jaggli commented Nov 29, 2018

Thank you. Ok we will:

  • keep the sequence
  • remove the restriction

@jaggli jaggli removed the Needs clarification Blocked - additional information required. label Nov 29, 2018
@jaggli jaggli closed this as completed Dec 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Missing functionality and changes
Projects
None yet
Development

No branches or pull requests

4 participants