<blockquote>
<p><a class="user-mention" data-hovercard-user-id="301810" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a> what do you think about PRiVCY class name? I'd go with Privcy.</p>
</blockquote>
<p>As general Java class naming style, <code>Privcy</code> would indeed be the way to go, but our convention here in bisq-assets has been to have the class name match precisely the spelling and capitalization of the asset as their promoters refer to it in their materials. Looking around the PRiVCY website, I see that they're quite consistent in that spelling, so let's keep it as-is in the PR. Basically, they've followed that convention, so it's all good.</p>
<p>However, the use of the lowercase 'i' in the ticker symbol <code>PRiV</code> is not conventional. I just double-checked, and all asset ticker symbols are upper case, so let's not diverge from that here. If you're happy with the code otherwise, then you can just push an additional commit renaming that ticker symbol. Or <a class="user-mention" data-hovercard-user-id="38500288" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/privcycoin">@privcycoin</a> you can do the same of course.</p>
<p>Also <a class="user-mention" data-hovercard-user-id="431064" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/blabno">@blabno</a>, these conventions aren't written down anywhere explicitly other than this comment. Feel free to patch the <code>list-asset</code> doc with them if you like.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq-assets/pull/34#issuecomment-399516042">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtli-MKEXzn8MjT_GSxugPrHdnkFTks5t_SaqgaJpZM4UjnM0">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtt9MGLX7fbPIUGxqhe75bqHjMJiaks5t_SaqgaJpZM4UjnM0.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/bisq-network/bisq-assets/pull/34#issuecomment-399516042","url":"https://github.com/bisq-network/bisq-assets/pull/34#issuecomment-399516042","name":"View Pull Request"},"description":"View this Pull Request on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}</script>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/bisq-assets","title":"bisq-network/bisq-assets","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/bisq-assets"}},"updates":{"snippets":[{"icon":"PERSON","message":"@cbeams in #34: \u003e @cbeams what do you think about PRiVCY class name? I'd go with Privcy.\r\n\r\nAs general Java class naming style, `Privcy` would indeed be the way to go, but our convention here in bisq-assets has been to have the class name match precisely the spelling and capitalization of the asset as their promoters refer to it in their materials. Looking around the PRiVCY website, I see that they're quite consistent in that spelling, so let's keep it as-is in the PR. Basically, they've followed that convention, so it's all good.\r\n\r\nHowever, the use of the lowercase 'i' in the ticker symbol `PRiV` is not conventional. I just double-checked, and all asset ticker symbols are upper case, so let's not diverge from that here. If you're happy with the code otherwise, then you can just push an additional commit renaming that ticker symbol. Or @privcycoin you can do the same of course.\r\n\r\nAlso @blabno, these conventions aren't written down anywhere explicitly other than this comment. Feel free to patch the `list-asset` doc with them if you like."}],"action":{"name":"View Pull Request","url":"https://github.com/bisq-network/bisq-assets/pull/34#issuecomment-399516042"}}}</script>
<script type="application/ld+json">{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [bisq-network/bisq-assets] List PRiVCY (PRiV) (#34)",
"sections": [
{
"text": "",
"activityTitle": "**Chris Beams**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@cbeams",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"bisq-network/bisq-assets\",\n\"issueId\": 34,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close pull request",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"PullRequestClose\",\n\"repositoryFullName\": \"bisq-network/bisq-assets\",\n\"pullRequestId\": 34\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/bisq-network/bisq-assets/pull/34#issuecomment-399516042"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 344879924\n}"
}
],
"themeColor": "26292E"
}</script>