+35
-4
lexicons/README.md
+35
-4
lexicons/README.md
···
123
123
"abstract": "We demonstrate...",
124
124
"authors": [
125
125
{
126
+
"did": "did:plc:abc123xyz456def789",
126
127
"name": "Dr. Jane Smith",
127
-
"orcid": "0000-0002-1825-0097",
128
-
"affiliation": "Stanford University"
128
+
"orcid": "0000-0001-2345-6789",
129
+
"affiliation": "Department of Molecular Biology, Stanford University",
130
+
"email": "jane.smith@stanford.edu"
131
+
},
132
+
{
133
+
"did": "did:plc:xyz789def456abc123",
134
+
"name": "Prof. John Doe",
135
+
"orcid": "0000-0002-3456-7890",
136
+
"affiliation": "Institute of Genetics, MIT",
137
+
"email": "john.doe@mit.edu"
129
138
}
130
139
],
131
140
"publication": "at://did:plc:abc123/at.scholarly.publication/nature",
···
143
152
"$type": "at.scholarly.manuscript",
144
153
"title": "Novel Machine Learning Architecture",
145
154
"abstract": "We propose...",
146
-
"authors": [{ /* personRef */ }],
155
+
"authors": [
156
+
{
157
+
"did": "did:plc:ml789researcher456",
158
+
"name": "Dr. Alice Johnson",
159
+
"orcid": "0000-0003-4567-8901",
160
+
"affiliation": "Computer Science Department, UC Berkeley",
161
+
"email": "alice.johnson@berkeley.edu"
162
+
}
163
+
],
147
164
"publication": "at://did:plc:xyz789/at.scholarly.publication/arxiv",
148
165
"submittedDate": "2024-02-01T00:00:00Z",
149
166
"status": "submitted",
···
199
216
{
200
217
"$type": "at.scholarly.manuscript",
201
218
"title": "Neural Architecture Search at Scale",
202
-
"authors": [{ /* personRef */ }],
219
+
"authors": [
220
+
{
221
+
"did": "did:plc:neuralnet456researcher",
222
+
"name": "Dr. Robert Chen",
223
+
"orcid": "0000-0004-5678-9012",
224
+
"affiliation": "AI Research Lab, Google DeepMind",
225
+
"email": "robert.chen@deepmind.com"
226
+
},
227
+
{
228
+
"did": "did:plc:coauthor789mlexpert",
229
+
"name": "Dr. Maria Garcia",
230
+
"orcid": "0000-0005-6789-0123",
231
+
"affiliation": "Department of Computer Science, Carnegie Mellon University"
232
+
}
233
+
],
203
234
"publication": "at://did:plc:pub/at.scholarly.publication/neurips-proceedings",
204
235
"event": "at://did:plc:org/at.scholarly.event/neurips-2024",
205
236
"submittedDate": "2024-05-15T00:00:00Z",
+2
-2
lexicons/definition/definition.json
+2
-2
lexicons/definition/definition.json
···
25
25
},
26
26
"personRef": {
27
27
"type": "object",
28
-
"description": "Reference to a person (author, reviewer, or editor) with their identifying information. This is used inline when listing manuscript authors or in places where you need to cite someone without requiring them to have a full profile record. Only name is required, but ORCID is strongly recommended to disambiguate people with common names. Used in: at.scholarly.manuscript (authors list), at.scholarly.version (authors list).",
28
+
"description": "Reference to a person (author, reviewer, or editor) with their identifying information. This is the primary way to reference people in the AT Protocol scholarly ecosystem. The DID is strongly recommended as the fundamental identifier linking to their full profile record, but is optional to accommodate people without AT Protocol accounts. ORCID is also strongly recommended to disambiguate people with common names. Used in: at.scholarly.manuscript (authors list), at.scholarly.version (authors list), and anywhere people need to be referenced.",
29
29
"required": [
30
30
"name"
31
31
],
···
33
33
"did": {
34
34
"type": "string",
35
35
"format": "did",
36
-
"description": "Optional Decentralized Identifier (DID) if this person has an AT Protocol account. Format: did:plc:abc123xyz. If provided, this links to their full author/reviewer/editor profile record. If not provided, this is just citation information."
36
+
"description": "The user's AT Protocol decentralized identifier (DID). This is the primary way to link to user accounts in the AT Protocol network. Format: did:plc:abc123xyz or did:web:example.com. When provided, this DID links to their full author/reviewer/editor profile record, enabling verification of identity and tracking of contributions across the scholarly ecosystem. Strongly recommended but optional to accommodate people without AT Protocol accounts."
37
37
},
38
38
"name": {
39
39
"type": "string",
+5
lexicons/editor/editor.json
+5
lexicons/editor/editor.json
···
14
14
"affiliation"
15
15
],
16
16
"properties": {
17
+
"did": {
18
+
"type": "string",
19
+
"format": "did",
20
+
"description": "The user's AT Protocol decentralized identifier (DID) - the primary identifier for this editor's account in the AT Protocol network. Format: did:plc:abc123xyz or did:web:example.com. Every AT Protocol user has exactly one DID that uniquely and permanently identifies them across all applications. This DID links to the editor's full profile, establishes their authority to make editorial decisions, and creates an immutable audit trail of their editorial actions. Strongly recommended but optional to accommodate editors without AT Protocol accounts."
21
+
},
17
22
"name": {
18
23
"type": "string",
19
24
"maxLength": 500,
+5
lexicons/reviewer/reviewer.json
+5
lexicons/reviewer/reviewer.json
···
14
14
"expertise"
15
15
],
16
16
"properties": {
17
+
"did": {
18
+
"type": "string",
19
+
"format": "did",
20
+
"description": "The user's AT Protocol decentralized identifier (DID) - the primary identifier for this reviewer's account in the AT Protocol network. Format: did:plc:abc123xyz or did:web:example.com. Every AT Protocol user has exactly one DID that uniquely and permanently identifies them across all applications. This DID links to the reviewer's full profile, allows verification of their credentials, and enables tracking of their peer review contributions while respecting confidentiality settings. Strongly recommended but optional to accommodate reviewers without AT Protocol accounts."
21
+
},
17
22
"name": {
18
23
"type": "string",
19
24
"maxLength": 500,