I would consider defining a new ABCorp:primaryKey property as a subproperty of dcterms:identifier. This will give the necessary semantics for your code
to understand it is dealing with a primary key of the ABCorp. If not enough, you can also define a new resource ABCorp:TableReference to describe how one would map the key given in RDF to the right SQL table in the right DB on the right server.
/Andrew
dcterms:identifier
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
From: Jad El-Khoury <jad@xxxxxx>
To: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
Date: 06/01/2018 05:58 AM
Subject: [lyo-dev] dcterms:identifier or oslc:shortId
Sent by: lyo-dev-bounces@xxxxxxxxxxx
Hi
I need to have a property that uniquely identifies a resource, which is not its URI (for internal usage, so it is easy to map the resource URI to the internal database key).
Any tips on a standard RDF property for such a property?
from http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA,
I can see either dcterms:identifier or oslc:shortId.
Is there a reason NOT to use dcterms:identifier, which to me seems more common/standard.
One argument is that dcterms:identifier is expected to “identify the resource by means of a string conforming to a formal identification system”.
that is, unless you have a such a “formal system” (in my understanding a database key is not), dcterms:identifier is not appropriate.
regards
______________________________
Jad El-khoury, PhD
KTH Royal Institute of Technology
School of Industrial Engineering and Management, Mechatronics Division
Brinellvägen 83, SE-100 44 Stockholm, Sweden
Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
jad@xxxxxx,
https://www.kth.se/profile/jad
_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/lyo-dev
