Add recommendations for the identifier format - #17
Merged
Conversation
rakhimov
force-pushed
the
name-format
branch
2 times, most recently
from
December 14, 2016 20:23
c66391d to
6d6a902
Compare
These are additions to the general recommendations for the MEF users and tools to use and process identifiers in a portable way. The recommendations are the same as proposed at the workshop and taken from the experience with SCRAM. To increase portability (especially, internationalization), the suggestions are based on W3 XML schema datatype specifications. The identifier specification is based on the XML NCName. It is worth noting that the name specification prohibits "period" because the MEF "references" specification relies on "period" as a scope resolution operator. The rest of suggestions are based on how most modern XML libraries and tools can handle the XML input, so it should not cause any issues for modern software to provide these guarantees/conformance.
rakhimov
force-pushed
the
name-format
branch
from
February 16, 2017 04:54
9dcbf3b to
5a6b4e9
Compare
cfolleau
approved these changes
Feb 16, 2017
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
These are additions to the general recommendations
for the MEF users and tools
to use and process identifiers in a portable way.
The recommendations are the same as proposed at the workshop
and taken from the experience with SCRAM.
To increase portability (especially, internationalization),
the suggestions are based on W3 XML schema datatype specifications.
The identifier specification is based on the XML NCName.
It is worth noting that the name specification prohibits "period"
because the MEF "references" specification relies on "period"
as a scope resolution operator.
The rest of suggestions are based on
how most modern XML libraries and tools can handle XML input,
so it should not cause any issues
for modern software to provide these guarantees/conformance.