Remove namespacing in base specification #30
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
I'm 👍 for removing namespaces in elements since they are not currently used, unless someone else has an reason they should stay (@zdne?). I think we should hold off on a formal way to do this unless/until we find a need for it. |
Member
There was a problem hiding this comment.
are they (namespace documents) going to be called profiles from now on?
Contributor
Author
There was a problem hiding this comment.
I think if we move to profiles, it seems like they should be called such, though I'm definitely open to suggestions here.
zdne
added a commit
that referenced
this pull request
Dec 7, 2015
Remove namespacing in base specification
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.