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.

Sign up for GitHub

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

Jump to bottom

Unnecessary finding: "Difference found in attribute name" when reference attribute is empty and vendor removes it #11

Open

tstephen opened this issue Oct 25, 2014 · 1 comment

Assignees

Labels

Contributor

tstephen commented Oct 25, 2014

Consider this excerpt from the A.1.0 reference model

  <semantic:sequenceFlow sourceRef="_93c466ab-b271-4376-a427-f4c353d55ce8" targetRef="_ec59e164-68b4-4f94-98de-ffb1c58a84af" name="" id="_e16564d7-0c4c-413e-95f6-f668a3f851fb"/>

The Yaoqiang 2 model writes the same thing as:

  <semantic:sequenceFlow id="_e16564d7-0c4c-413e-95f6-f668a3f851fb" sourceRef="_93c466ab-b271-4376-a427-f4c353d55ce8" targetRef="_ec59e164-68b4-4f94-98de-ffb1c58a84af"/>

The xml-compare tool reports:

Difference found in attribute name
which is syntactically true but not semantically important so I propose to suppress the finding in this situation.

The text was updated successfully, but these errors were encountered:

tstephen added the enhancement label

tstephen self-assigned this

Contributor Author

tstephen commented Oct 29, 2014

Webmeeting 29 Oct 2014

Further analysis to be done:

Ensure non-null attribute continues to be flagged as an issue
Ensure XML spec treats empty attribute and unspecified attribute as equivalent. esp in the case on non-string attributes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment