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

Confusing Xpath expressions of the *md file #139

Open
PaulaRodrigo-Geograma opened this issue Apr 18, 2018 · 5 comments
Open

Confusing Xpath expressions of the *md file #139

PaulaRodrigo-Geograma opened this issue Apr 18, 2018 · 5 comments
Assignees

Comments

@PaulaRodrigo-Geograma
Copy link
Contributor

There are many ATS with the Xpath expressions defined without the format of the *md file itself and it is confusing to understand in terms of its implementation in an executable test.

For example:

https://github.com/inspire-eu-validation/view-service/blob/master/layer-metadata/layer-style-name.md#contextual-xpath-references

@michellutz
Copy link

Do you mean that the XPath references are not properly formatted using the MD syntax?

@PaulaRodrigo-Geograma
Copy link
Contributor Author

I don't mean the XPATH expression, I only refer to the format of the * md file of this ATS (and many others).

It seems that these md's are not written correctly, and the XPATH expressions in the "# contextual-xpath-references" section do not maintain the structure of the table:

Abbreviation / XPath expression / Parameter value

Texts leave their cells and sometimes it is confusing

@michellutz
Copy link

OK, this is what I meant - the issue is the formatting of the md file.

I think in this case, please simply correct the table formatting and create a pull request for an update.

@michellutz
Copy link

[2017.4 meeting 2018-04-19] The JRC contractor will correct such obvious formatting mistakes in their proposal for a restructuring/refactoring to be discussed in the next sub-group meeting.

@michellutz
Copy link

This has been implemented in the ATS revision for view services. So the issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants