oslc-promcode — archive

Re: Fw: [oslc-core] Specification authoring tools + usage of vocabs and shapes

From: Steve Speicher <[email protected]>
To: [email protected]
Date: Fri, 30 Jan 2015 12:58:00 -0000

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 <[email protected]> To: Steve K Speicher/Raleigh/IBM@IBMUS Cc: "[email protected]" <[email protected]>, Arthur Ryman <[email protected]> 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>Name: <code>TemplateClass</code></li> <li>URI: <code> http://open-services.net/ns/xxx#TemplateClass </code></li> <li>Summary: 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>Name: <code>TemplateClass</code></li> <li>URI: <code> http://A.net/B </code></li> <li>Summary: 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>Name: <code> TemplateClass </code></li> <li> Target Resource URI: <code> http://open-services.net/ns/xxx#TemplateClass </code></li> <li> Shape Resource URI: <code> http://A.net/B </code></li> <li>Summary: 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 ! From: [email protected] [ mailto:[email protected] ] On Behalf Of Steve K Speicher Sent: Thursday, January 29, 2015 11:35 PM To: Funakoshi Kazuhiro( ?? ?? ) Cc: [email protected]; Arthur Ryman Subject: RE: [oslc-promcode] Re: Fw: [oslc-core] Specification authoring tools + usage of vocabs and shapes Hi Kaz, I have responded below > From: Kazuhiro Funakoshi < [email protected] > > To: Steve K Speicher/Raleigh/IBM@IBMUS > Cc: Arthur Ryman < [email protected] >, " [email protected] " > < [email protected] > > Date: 01/28/2015 09:27 PM > Subject: RE: [oslc-promcode] Re: Fw: [oslc-core] Specification authoring > tools + usage of vocabs and shapes > > Dear Steve, > > I'm Kaz from PROMCODE-TC. We are using your ReSpec and think it's a really > productive tool. > > I have two questions: > > * for shape documents, following tag provides URI, but it seems a URI to the > resource in namespace, not shape URI. Is it a intended > behavior? > <div title='RDF Shape for Template' > data-include='./template-spec-shape.ttl' > data- > data-include-sync='true' > data-include-replace='true' > data-include-format='html'></div> Can you elaborate on what you mean that the tag provides URI? The attribute "data-include" takes a parameter the file name the document to include and the attribute 'data-oninclude' instructs the tool which function to use to process the document it loads, which using the function name of 'shapeToSpec' invokes the function I wrote to transform the shape into ReSpec/HTML. This seems to work fine in the template spec and I used it yesterday for the discovery spec. http://sspeiche.github.io/respec/examples/oslc/template-spec.html > * my another question is the trick you are using at oslc-core svn repository > to provide html file. > In our repository, clicking html files just gives us html source code not > rendered html. > Is it possible to do that with TC member privileges? > e.g. < https://tools.oasis-open.org/version-control/browse/wsvn/oslc- > promcode/shape/trunk/shape.html> > > Currently, when I updated our spec on svn, then copy its js rendered html to TC wiki. > If we can see the html document from repository, then it can be much easier. > You simply need to set some svn metadata about the file in the repository. 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" See thread on core TC about this: http://markmail.org/message/g3tfr6sr55ysvdct Also on how to have your client set it by default: http://stackoverflow.com/questions/4100121/serving-html-thru-svn-server Hope this helps, Steve > Thank you in advance, > Kaz > >