[OASIS Issue Tracker] (OSLCCORE-42) Consider switching ReSpec reference repo

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61135#comment-61135 ] 

Nick Crossley commented on OSLCCORE-42:
---------------------------------------

They could be - but you might want to check if you even still need them. The second one you show is just a comment, so can be removed. The first includes some Javascript functions for parsing and handling RDF - but it is quite likely that all your usage is via ReSpec. Search your source for calls to N3.anything - if there are none, you can probably just delete that line as well.

> Consider switching ReSpec reference repo
> ----------------------------------------
>
>                 Key: OSLCCORE-42
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-42
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>
> In OASIS OSLC specs up to now, we have been using the following URI as the reference for ReSpec:
> https://sspeiche.github.io/respec/builds/oasis/respec-oasis-common.js
> This is Steve Speicher's repository. While Steve did excellent work on the initial development of an OASIS variant of ReSpec, it is not clear that he now has the time available to make further changes that we need.
> In the long term, we need a neutral host for this repo, preferably one managed by OASIS. In the short term, before an OASIS host is available, we need to make changes to support upcoming public reviews.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)