-
Notifications
You must be signed in to change notification settings - Fork 7
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
TG2-Some terminology for Target source authority #160
Comments
I would default universally (examples, reference, notes) to the simpler "specified authority" |
I agree.
…On Mon, Sep 3, 2018 at 10:57 AM Lee Belbin ***@***.***> wrote:
I would default universally (examples, reference, notes) to the simpler
"specified authority"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#160 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAcP6_h3wEMbuSXi6paM7u0mcawyVGLNks5uXGJUgaJpZM4WWdAs>
.
|
OK - I will change them all to specified target source authority and close this issue |
All have been altered to refer to "specified" source authority |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In most of the Test Prerequisites we refer to "specified target source authority" (#20 #21 #22 #25 #26 #27 #28 #38 #41 #45 #46 #48 #50 #53 #56 #57 #59 #60 #62 #63 #70 #71 #73 #77 #80 #81 #83 #90 #91 #94 #95 #97 #106 #115 #116 #118 #122 #123 #133 #139) or "specified source vocabulary" (#63 #104),
but in many of the descriptions we use "designated source authority" (#22 #28 #63 #70 #77 #81 #83 #122 #123 #139 ) or "designated geographic authority" (#118 )
From the above we are very consistent in the Test Prerequisite - perhaps we should change #63 and #104 .
In the Descriptions we are consistent with "designated" - should we change this to "specified" (we don't have specified in any description at the moment) and should we change #118 to "designated source authority"
The text was updated successfully, but these errors were encountered: