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

Relax tenant id format #322

Merged
merged 1 commit into from
Jul 30, 2019
Merged

Relax tenant id format #322

merged 1 commit into from
Jul 30, 2019

Conversation

mwear
Copy link
Member

@mwear mwear commented Jul 24, 2019

This PR relaxes the tenant id format so that it can begin with a lowercase letter or number. Previously, it was required to start with a lowercase letter. This change was discussed in issue #316.

My BNF-fu might not be quite up to snuff, so please double check it and let me know if it needs any adjustments.

This commit relaxes the tenant id format so that it can begin with
a lowercase letter or number. Previously, it was required to start
with a lowercase number.
@danielkhan danielkhan merged commit 428670e into w3c:master Jul 30, 2019
@mwear mwear mentioned this pull request Aug 1, 2019
lcalpha = %x61-7A ; a-z
```

**Note**: Identifiers MUST begin with a lowercase letter, and can only contain lowercase letters (`a`-`z`), digits (`0`-`9`), underscores (`_`), dashes (`-`), asterisks (`*`), and forward slashes (`/`).
**Note**: Identifiers MUST begin with a lowercase letter or a digit, and can only contain lowercase letters (`a`-`z`), digits (`0`-`9`), underscores (`_`), dashes (`-`), asterisks (`*`), and forward slashes (`/`).

Choose a reason for hiding this comment

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

I was trying to wrap my head around this and think there's a doc glitch here.

this phrase 'or a digit' here should apply both to simple and multi-tenant encodings. However, line 279 wasn't updated so basically the text doesn't match the abnf.

I think either the relaxing should apply in both abnf (ex also 279) or this special case about "or a digit" should move to the next paragraph which talks about the second encoding.

Choose a reason for hiding this comment

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

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.

5 participants