RE: [oslc-promcode] Re: Including files in specifications for PROMCODE

[Arthur Ryman <ryman@ca.ibm.com>]

Kaz,

Sounds right, except that there is no need to use the WP-abbrev in the RDF 
URI. We can redirect the RDF URI to any document URI at OASIS. I suggest 
the following shorter RDF URIs for shapes:

http://open-services.net/ns/promcode/shapes/1.0/artifact
http://open-services.net/ns/promcode/shapes/1.0/workitem
etc.

These would redirect to
http://docs.oasis-open.org/oslc-promcode/artifactshape/v1.0/artifactshape.tt
l
http://docs.oasis-open.org/oslc-promcode/workitemshape/v1.0/workitemshape.tt
l
etc.

Since we have a separate Turtle file for each shape, the @base is like:

@base <http://open-services.net/ns/promcode/shapes/1.0/artifact>

and the relative URIs are like:

<#isPartOf>
_________________________________________________________
Arthur Ryman
Chief Data Officer
SWG | Rational
905.413.3077 (phone) | 416.939.5063 (cell)
IBM InterConnect 2015




From:   Kazuhiro Funakoshi <k-f@bk.jp.nec.com>
To:     Arthur Ryman/Toronto/IBM@IBMCA
Cc:     "robin@oasis-open.org" <robin@oasis-open.org>, 
"oslc-promcode@lists.oasis-open.org" <oslc-promcode@lists.oasis-open.org>, 
Steve K Speicher <sspeiche@us.ibm.com>
Date:   12/18/2014 03:05 AM
Subject:        RE: [oslc-promcode] Re: Including files in specifications 
for PROMCODE
Sent by:        <oslc-promcode@lists.oasis-open.org>



Arthur,

I'm fine to do that as long as [1] redirects to these paths.
Since each of rdf(and ttl) has @base as [1] and it redirects to the path 
as
you wrote respectively, I don’t need to care about path at this moment, 
do
I?

However, I have to change shape resource name, I think.
e.g.
Currently(in our WebSVN version), Artifact shape resource has stable path 
as
[2] (I assume [2] will be redirected to [3] in case of turtle/text).
The minimum work should be:
  * change the name Artifact.ttl into artifactshape.ttl
  * change <Artifact> to <artifactshape>
  * change <Artifact#isPartOf> to <artifactshape#isPartOf>,
right?

I will do this change after next TC conf next week.

[1] http://open-services.net/ns/promocode/shapes/1.0/shape
[2] http://open-services.net/ns/promcode/shapes/1.0/shape/Artifact
[3]
http://docs.oasis-open.org/oslc-promcode/artifactshape/v1.0/artifactshape.tt

l

--
Kaz

-----Original Message-----
From: Arthur Ryman [mailto:ryman@ca.ibm.com]
Sent: Thursday, December 18, 2014 3:46 AM
To: Funakoshi Kazuhiro(船越 和大)
Cc: robin@oasis-open.org; oslc-promcode@lists.oasis-open.org; Steve K
Speicher
Subject: RE: [oslc-promcode] Re: Including files in specifications for
PROMCODE

Kaz,

The rules for URIs are described in [1]. That document explains how to 
build
up the URI. One of the components of the URI is called work product
abbreviation, WP-abbrev. We therefore need to define a WP-abbrev for each
work product, e.g. each shape file.

I suggest we use the following WP-abbrevs for shape documents:
projectshape
artifactshape
workitemshape
scopeitemshape

etc.

The latest version URIs would be:
http://docs.oasis-open.org/oslc-promcode/projectshape/v1.0/projectshape.rdf

http://docs.oasis-open.org/oslc-promcode/artifactshape/v1.0/artifactshape.rd

f
http://docs.oasis-open.org/oslc-promcode/workitemshape/v1.0/workitemshape.rd

f
http://docs.oasis-open.org/oslc-promcode/scopeitemshape/v1.0/scopeitemshape
.
rdf

If you prefer, you can use camel case, e.g. ProjectShape.

Robin - please confirm I have this right. Thx.

[1] http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html
_________________________________________________________
Arthur Ryman
Chief Data Officer
SWG | Rational
905.413.3077 (phone) | 416.939.5063 (cell) IBM InterConnect 2015