Skip to content

Conversation

@michaelhkay
Copy link
Contributor

Fix #1337

I was half-expecting this change to have repercussions, but in practice it seems very clean.

There are probably more places that should change, e.g. use "xs:boolean item" rather than "xs:boolean value", but we can deal with them as we come to them.

@ChristianGruen
Copy link
Contributor

Looks good.

There are probably more places that should change, e.g. use "xs:boolean item" rather than "xs:boolean value", but we can deal with them as we come to them.

Fair enough (and it’s still correct to call those items values).

Don changes (XPathXQuery.xml, introduction.xml, fragment.xml):
I have attempted to update these files with the latest terminology
(mainly changing "simple value" to "atomic value" and related changes.)
(mainly changing "simple value" to "atomic item" and related changes.)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stet? This fiddles with a changelog.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if javacc.xsl was ever updated to support the XPath 3.1 grammar, it certainly hasn't been updated to support 4.0. (I believe it is code to generate a javaCC parser from the EBNF grammar).

@michaelhkay michaelhkay merged commit e573858 into qt4cg:master Sep 3, 2024
@michaelhkay michaelhkay added the Completed PR has been applied, tests written and tagged, no further action needed label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Completed PR has been applied, tests written and tagged, no further action needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Atomic value → atomic item

3 participants