Comments (7)
- Agree to the version, should be of type string I think, or some type of pattern that forces the user to use semver type notation (I personally prefer to allow people to use their own versioning scheme).
- Also agree to the copyright, but I would replace it with a license
- Also agree to the author not having to be an email address
In addition I would like to propose to put a maxOccurs=1 on all of the elements below Info, this helps tell the tooling that there will at most be one instance of each and therefore a singular field can be used instead of a list. Assuming the idea is no to have multiple "version", multiple "author" etc...
from ids.
As far as I know, in a XSD file is "maxOccurs=1" and "minOccurs=1" by default. But making it explicit is good style.
from ids.
I also think that the default value is 1 and except for the element version, all would then be present once per info element. But the info element content (sequence) can occur several times (if I have understood the schema correctly).
from ids.
Made some minor updates in 0.4.4 (now online)
- version changed to string
- made some more elements optional, but 'ifcversion' and 'name' stayed required. Ifcversion because otherwise it does not work, name because it seems to make sense to at least give the set of specifications a name.
- to make it link to BCF 'assignedTo' an email address is strongly recommended. We could lose the restriction in the XSD, but would need to document that this is a strong recommendation to use a email address here
from ids.
I also think that the default value is 1 and except for the element version, all would then be present once per info element. But the info element content (sequence) can occur several times (if I have understood the schema correctly).
I think the info element has the (impicit) definition minOccurs="1" maxOccurs="1" and occurs only once.
The maxOccurs="unbounded" in the sequence definition only indicates the number of occurrences of the elements in the sequence (which are in turn limited to themselves).
So each element can appear once. I think the definition is as far as desired.
from ids.
Made some minor updates in 0.4.4 (now online)
* version changed to string * made some more elements optional, but 'ifcversion' and 'name' stayed required. Ifcversion because otherwise it does not work, name because it seems to make sense to at least give the set of specifications a name. * to make it link to BCF 'assignedTo' an email address is strongly recommended. We could lose the restriction in the XSD, but would need to document that this is a strong recommendation to use a email address here
Thanks for update.
'name' element as required makes sense.
For the author element I would then separate it and not mix things up. The author element should be free text (prefered 'optional'; it makes sense to declare it in practice, but should not be 'required' by the specification).
For BCF or other exchange mechanisms there should be a separate element. 'email' or maybe something more neutral like 'contact', 'exchange channel', 'exchange interface' or something similar. However, this should not be limited to email addresses. Other mechanisms such as web services or similar are also imaginable (in the future?). Then the element content will not be an email address.
from ids.
This is now processed in 0.5.0
from ids.
Related Issues (20)
- Shortcoming for validation of PredefinedType setting in entity facet HOT 5
- Property Test Cases HOT 2
- (reminder to) change from IFC4X3 to IFC4X3_ADD2 HOT 7
- Notes on custom restriction type
- Prohibited specification with an optional requirement HOT 2
- Inaccurate using of word "entity". HOT 3
- IDS Rule - Floating point numbers are compared with a 1e-6 tolerance 1/4 HOT 1
- Make name of attributeType string HOT 3
- Classification Facet behavior is not full HOT 6
- Some issues in test-cases
- test-case error? pass-occurrences_override_the_type_classification_per_system_1_3 HOT 4
- pass-the_container_may_be_indirect, should it really pass?
- fail-an_enumeration_matches_case_sensitively_1_3.ids
- Applicability logic HOT 6
- Construction phase/LOI related IDS Check HOT 2
- you can delete this sorry
- Model Element Author specification using IDS HOT 1
- IDS XSD Specification / Versions HOT 3
- Very bad documentation for XSD validation HOT 4
- IFC 4x3 Version conformity HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ids.