- From: Andrea Perego <andrea.perego@jrc.ec.europa.eu>
- Date: Thu, 22 Dec 2016 11:23:24 +0100
- To: Catonano <catonano@gmail.com>
- Cc: public-lod@w3.org
The W3C ADMS vocabulary provides a mechanism to specify primary identifiers (via dct:identifier) and secondary/alternative identifiers (via adms:Identifier [1]). About schema.org, there's currently work under-way on this: http://webschemas.org/identifier See also the relevant issue: https://github.com/schemaorg/schemaorg/issues/1286 After all, the main point is which kind of information you would like to record. If you want to describe the identifier itself, adms:Identifier allows you to do that. But if you just want to record the "type" of identifier, what you need is either a specific property for identifier type (e.g., prims:doi / bibo:doi), or to model the identifier type as a datatype, which can be used for more generic properties (as dct:identifier). As a matter of fact, there's currently no best practice or reference vocabulary for expressing identifiers in RDF. Hope this helps Andrea ---- [1]https://www.w3.org/TR/vocab-adms/#identifier On 21/12/2016 16:47, Catonano wrote: > Hello, > > in my dataset there are several IDs for each record and I'm working on > publishing this dataset as linked data. > > Is there any dictionary provisioning means to express IDs ? Or have I to > make my own dictionary ? > > The reason why there are several IDs for each row, is that this is a > collection of items coming from several different databases, differently > operated through the years. > > It's a collection of political texts ranging from the forties to today. > > The attributes of each record are quite simple, I managed to map them to > Dublin Core and Schema.org properties easily. > > But this IDs thing is harder. > > Thanks for any hint -- Andrea Perego, Ph.D. Scientific / Technical Project Officer European Commission DG JRC Directorate B - Growth and Innovation Unit B6 - Digital Economy Via E. Fermi, 2749 - TP 262 21027 Ispra VA, Italy https://ec.europa.eu/jrc/ ---- The views expressed are purely those of the writer and may not in any circumstances be regarded as stating an official position of the European Commission.
Received on Thursday, 22 December 2016 10:24:11 UTC