Clarified naming rules for user defined callables and added list for reserved and deprecated namespaces

[JoelBergstrand]

Changes and clarification from PR.

[NataliaIvakina]

A very good clarification and addition. Thank you, @JoelBergstrand!
I have only one question: For which Neo4j versions is this valid?

[JoelBergstrand]

@NataliaIvakina, this will be valid for 2025.11 and forward. Some of it applies to earlier version as well but not the information about deprecations.

[NataliaIvakina]

@NataliaIvakina, this will be valid for 2025.11 and forward. Some of it applies to earlier version as well but not the information about deprecations.

So, I assume we have to reflect this information in the Deprecations columns. Mark it with the Deprecated in 2025.11 label? Or just say 'Deprecated since 2025.10'?
@JoelBergstrand, could you please specify what exactly is applicable to earlier versions and which versions (5.x, 2025.01-2025.09), so I can transfer this to the 5.x and publish (main) branch?

Please do not merge this PR till 2025.10 docs are published.

[JoelBergstrand]

@NataliaIvakina, the reserved columns are correct for 5.x and 2025.x-10. It is only the mentions of deprecations that are new behavior in 2025.11.

I can leave the merging to you if you are okey with that.

[NataliaIvakina]

@NataliaIvakina, the reserved columns are correct for 5.x and 2025.x-10. It is only the mentions of deprecations that are new behavior in 2025.11.

I can leave the merging to you if you are okey with that.

Ok, nice! I'll take care of this PR, no probs. I'll also raise PRs against the 5.x and main branches and ping you to review them.

[Lojjs]

Do you think we want to mention explicitly that the deprecated namespaces will be restricted in the future or do you think that is easy to understand?

Apart from this question which I am unsure about, this documentation looks good I think.

[NataliaIvakina]

Do you think we want to mention explicitly that the deprecated namespaces will be restricted in the future or do you think that is easy to understand?

Apart from this question which I am unsure about, this documentation looks good I think.

@Lojjs hi! I think it's clear enough that the deprecated namespaces will remain deprecated in future releases.
But what exactly do you mean by 'the deprecated namespaces will be restricted'? Do we need to add extra details of what will happen to those deprecated namespaces?
If I read the text correctly, your user-defined function/procedure with the same name as a built-in procedure in a deprecated namespace will override the built-in procedure.

[neo4j-docops-agent]

This PR includes documentation updates
View the updated docs at https://neo4j-docs-java-reference-310.surge.sh

Updated pages:

• User-defined aggregation functions
• User-defined functions
• User-defined procedures

[JoelBergstrand]

@NataliaIvakina, I think what @Lojjs is referring to is that the namespaces are deprecated in the Cypher 25 version. So will be move to reserved in the next Cypher version whenever that is. Maybe we should make that more apparent to the users.