Hi Jim & all,
So, I have a couple questions that I still feels are left unanswered and I hope you can help me clarify.
As background, we want in a project to define a company-specific domain vocabulary based on OSLC Core, and also extend any existing OSLC specifications when
necessary.
I am missing some guidelines on how to go about defining a domain. Specifically I wonder about the following:
1.
I understood from your(Jim) comments that a domain specification can reuse any Core Common Property, and then simply override any of the constraints defined
in OSLC Core. For example, dcterms:creator be changed from the current Zero-or-many to Exactly-One.
Is there a risk in deviating from OSLC Core?
Is there a need to highlight in the specs if a certain constraint has been overridden, in order to keep track of the changes?
Is there any aspect of the common properties that a domain specs ought not to change?
2.
Any guidelines and/or templates on how one ought to define a vocabulary?
Specifically, when it comes to defining constraints on a resource, I notice in the OSLC domain specifications (and Core) that the properties tables are limited
to the following constraints: Occurs, read-only, value-type, Representation, Range & Description.
Is there a problem if a domain specification chooses to define additional Property Constraints (such as defaultValue) in the tables?
I am afraid I might be confusing the concepts of ResourceShapes and Vocabularies.
I suspect such issues are trivial for an expert in linked data, but maybe not for someone with a “closed-world” view (which I experience are most users of OSLC
– including myself). So, I wondering if such questions are worth detailing somewhere. (Then I have something to refer to in my arguments
J )
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
,
www.kth.se
From: Jim Amsden [mailto:]
Sent: 04 February 2016 20:50
To: Jad El-Khoury
Cc:
Subject: Re: [oslc-core] Review of OSLC Core Vocabulary 3
Jad,
Responses in your notes in the attached. Lots of good catches and I've applied all the updates.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
From: Jad El-Khoury <>
To: "" <>
Date: 02/03/2016 06:06 PM
Subject: [oslc-core] Review of OSLC Core Vocabulary 3
Sent by: <>
Hi,
Attached are my review comments on the “OSLC Core Vocabulary”. A bit late, but hope it’s not too late!
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
,
www.kth.se
[attachment "OSLC Core Vocabulary 3.pdf" deleted by Jim Amsden/Raleigh/IBM]
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
