Skip to content

Conversation

@fgalan
Copy link
Member

@fgalan fgalan commented Nov 29, 2016

No description provided.

places where such characters are not allowed. For example, some persistence backends are based in databases which
doesn't accept whitespaces or non-ASCII characters in table databases.
* IDs may appear as part of URLs (e.g. the URL identifying an entity at [Context Broker](../context_broker.md) and
using non-ASCII characters in that places makes these URL more complex.
Copy link
Member Author

Choose a reason for hiding this comment

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

Probably this is the weaker part of the PR. More arguments or reinforcement of the existing ones are welcome.

who decides when and how it may change (if it is allowed to do it at all). However, note that we
are not using UUID in this documentation for didactic reasons but in real usage use case
you should consider this recommendation.

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe a fouth point about the unconvenience of using "_" in IDs should be included. Taking into account that the part that most has "suffered" this in the past (and present :) in the one about persistence done by Cygnus probably @frbattid is the best one to contribute.

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

Successfully merging this pull request may close these issues.

3 participants