-
Notifications
You must be signed in to change notification settings - Fork 15
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
onlineResource 2.0 #50
Comments
In our effort to conform to naming standards for mdJSON elements we adopted a convention to capitalize acronyms. What if the element name is an acronym, as uri above?
|
Why did we change this to So:
|
Great, I just went through and changed them all to upper case per our earlier discussion.
…Sent from my iPhone
On Jan 17, 2017, at 10:19 AM, Josh Bradley ***@***.***> wrote:
Why did we change this to resourceURI? I prefer just plain uri. If the property name is a single acronym, I'd just lowercase the whole thing. I don't really care as long as it's consistent. In fact, why don't we just treat acronyms as lowercase words. That follows KISS logic.
So:
uri
resourceUri
resourceJsonUri
resourceJsonUriUsa
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
My bad. Do you want to leave them upper-cased? |
All choices are bad. Can't start name with upper case, don't want mixed case, if acronym not first word pushed to camel case. So no right answer.
If uppercase, acronym cannot be first word.
If lowercase, acronym must be first word.
Your choice.
…Sent from my iPhone
On Jan 17, 2017, at 12:34 PM, Josh Bradley ***@***.***> wrote:
My bad. Do you want to leave them upper-cased?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
That's why I was suggesting that we just treat them as "normal" words. Just camel-case like any other word. |
Changes:
see XML example responsibleParty -3.xml
The text was updated successfully, but these errors were encountered: