#276: Fixed prefix declarations in test cases and adjusted examples to use .com instead of .org #605
Conversation
…o use .com instead of .org
| sh:path ex:fullName ; | ||
| sh:values <b>[ | ||
| sh:prefixes <http://example.org/ns> ; | ||
| sh:prefixes <http://example.com/ns> ; |
There was a problem hiding this comment.
(Why change .org to .com?)
Even better change - use http://example/.
It is specifically for this purpose.
".example" is recommended for use in documentation or as examples.
It is registered and fixed. It does not have a website at that address by design.
There was a problem hiding this comment.
The choice between .org and .com was made before, not by me. I am merely aligning these test cases with all others.
There was a problem hiding this comment.
The domains example.org. and example.com. (and example.net.) are just as acceptable as example. See RFC 2606 section 3.
Things do get more entertaining when trying to test (and not just document) with these domains, as discussed in RFC 6761 section 6.5, where it is said:
The domains "example.", "example.com.", "example.net.",
"example.org.", and any names falling within those domains, are
special in the following ways:
1. Users SHOULD understand that example names are reserved for use
in documentation.
2. Application software SHOULD NOT recognize example names as
special and SHOULD use example names as they would other domain
names.
3. Name resolution APIs and libraries SHOULD NOT recognize example
names as special and SHOULD NOT treat them differently. Name
resolution APIs SHOULD send queries for example names to their
configured caching DNS server(s).
There was a problem hiding this comment.
The choice between
.organd.comwas made before, not by me. I am merely aligning these test cases with all others.
I think it would have helped @afs (as well as myself) if the initial comment had noted that "adjusted examples to use .com instead of .org" was just a "make all the examples use the same .tld" alignment, and not any kind of judgement about .com being better than .org. That said, I'm wondering whether there is more value in varying the .tld than in unifying them.
There was a problem hiding this comment.
@afs may I ping you on this old PR?
To quote RFC 2606 section 2: ".example" is recommended for use in documentation or as examples.
That's a suggestion, not a blocker.
Closes #276