oslc-promcode — archive

[Kazuhiro Funakoshi]

Arthur, OK, I tried using ReSpec[1] as Steve suggested. The result is in our trunk. Workflow should be also changed as [2] and dotlit is not required any more(same for npm, nvm). I still use Markdown in these documents for editing. However, now no Turtle blocks or Markdown tables we need. Turtle files are now first class citizen and tables are automatically generated as html with ReSpec. This means no consistency problems left. This is done by adding that div block into Markdown and HTML headers are automatically inserted with my pandoc.sh(I changed it to include header.html at end of HTML header block). BTW, I met a thing is, Steve's ReSpec seems not accepts multiple oslc:range properties. Is this a correct behavior to ResourceShape 2.0? Because oslc:range seems not said to be oslc:Zero-or-one, and we have a property as promcode:producedFor from Artifact toward either ScopeItem or WorkItem. [1] e.g. http://tools.oasis-open.org/version-control/browse/wsvn/oslc-promcode/shape/ trunk/Artifact.html [2] https://wiki.oasis-open.org/oslc-promcode/shape/readme -- Kaz