Steve,
Class URI & Shape URI are good enough I think.
This modification is very nice and I appreciate it.
Thank you,
Kaz
From: oslc-promcode@lists.oasis-open.org [mailto:oslc-promcode@lists.oasis-open.org] On Behalf Of Steve K Speicher
Sent: Friday, January 30, 2015 9:57 PM
To: Funakoshi Kazuhiro(船越 和大)
Cc: oslc-promcode@lists.oasis-open.org; Arthur Ryman
Subject: RE: [oslc-promcode] Re: Fw: [oslc-core] Specification authoring tools + usage of vocabs and shapes
Kaz,
Ok, I understand better now.
I wonder if just having something simple like:
Name: TemplateClass
Class URI: http://open-services.net/ns/xxx#TemplateClass
Shape URI: http://open-services.net/ns/xxx/shapes/TemplateClass
Or would it be misleading to call it a Class (even though we are treating it as a class both in the RDFSchema sense and UML)?
Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web -> http://open-services.net
From: Kazuhiro Funakoshi <k-f@bk.jp.nec.com>
To: Steve K Speicher/Raleigh/IBM@IBMUS
Cc: "oslc-promcode@lists.oasis-open.org" <oslc-promcode@lists.oasis-open.org>, Arthur Ryman <ryman@ca.ibm.com>
Date: 01/29/2015 07:50 PM
Subject: RE: [oslc-promcode] Re: Fw: [oslc-core] Specification authoring tools + usage of vocabs and shapes
Steve,
Thank your for your reply.
> Can you elaborate on what you mean that the tag provides URI?
What I meant is the ReSPEC rendered URI field by using the tag.
In your example 6.2 Shape, it renders:
“””
<li><strong>Name:</strong> <code>TemplateClass</code></li>
<li><strong>URI: </strong> <code>http://open-services.net/ns/xxx#TemplateClass</code></li>
<li><strong>Summary:</strong> Shape for template resource</li>
“””(copied from my firefox inspector, and highlighted)
In my opinition, the human reader of the document might expect this URI is an URI of the shape resource rather than URI of the described resource.
In this case, your template-spec-shape.ttl does not have a base URI, so assume:
“””
@base <http://A.net/B>
<> a oslc:ResourceShape
…
Oslc:name “TemplateClass”
“””
then we should obtain:
<li><strong>Name:</strong> <code>TemplateClass</code></li>
<li><strong>URI: </strong> <code>http://A.net/B </code></li>
<li><strong>Summary:</strong> Shape for template resource</li>
Maybe the field name “URI” is misleading.
What about “Target Resource URI” and “Shape Resource URI” ?
Since the shape resource is not consumed only by ReSpec but also some other applications provided for checking violations, the user would like to know the URI of the shape resources.
“””
<li><strong>Name:</strong> <code>TemplateClass</code></li>
<li><strong>Target Resource URI: </strong> <code> http://open-services.net/ns/xxx#TemplateClass </code></li>
<li><strong>Shape Resource URI: </strong> <code>http://A.net/B </code></li>
<li><strong>Summary:</strong> Shape for template resource</li>
“””
> Here is a sample of the commands you need to run:
> $svn propset svn:mime-type text/html <filename>
> $svn commit -m "Serve html, as html"
Thank your !
I tried it with text/html for html file, and text/turtle for ttl files.
Now it works perfectly as I expected !