-
Notifications
You must be signed in to change notification settings - Fork 69
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
Possibly redundant "description" attrubute in the "semanticAttributes" attributeGroup #143
Comments
Questions about CME's message schema should be addressed to their support group. For one, they can tell you which version of the SBE standard it conforms to. |
Well... the question is not about CME SBE specification. I mentioned CME SBE to explain how did I find the Don't you think that the |
@ujos |
I mean why did you add the The problem is if you try adding the |
I understand that you believe that there "description" attribute is defined twice for the same type, causing a conflict. However, I don't see that for "simpleDataType". It has "description" as an attribute, but is does not include "semanticAttributes" attribute group. So "description" is only defined once for that type. Conversely, "semanticAttributes" is included in "fieldType" and "blockType", which do not independently define "description", so again I do not see a conflict. Which is not to say that the schema could not be improved. PRs will be considered. |
I have a problem using the Visual Studio for CME iLink3 SBE schema editing.
After I've added
semanticAttributes
to thesimpleDataType
,memberDataType
andcompositeDataType
elements, the VS started to complain about the duplicateddescription
attribute. In factsimpleDataType
,memberDataType
andcompositeDataType
have thedescription
attribute andsemanticAttributes
element has it as well.From my point of view the
description
tag is redundant forsemanticAttributes
, but I'm not the XML expert. Probably it is just a bug in the Visual Studio.Attached in the attachment.zip are:
The text was updated successfully, but these errors were encountered: