Prepare for SCRAPI #139
Prepare for SCRAPI #139
Conversation
OR13
requested review from
henkbirkholz,
ad-l,
fournet and
yogeshbdeshpande
as code owners
|
Re the SCRAPI I-D reference, it does not appear to be in the IETF Datatracker system at all and noticed when it wasn't listed or clicked on a link to search by I-D name and it returned no results, @OR13. That is why I asked about this on the mailing list. https://mailarchive.ietf.org/arch/msg/scitt/AqHH6OUrc2Xzj81JI-fD4IUB91U/ Don't we need to take care of that issue for the short-hand references to work at all? Can it not be added to the tracker in advance of being adopted by the WG? (It seems some are added and "owned" by authors and not associated with the target WG in advance in some or not all cases. Sorry, I am new here. UPDATE: I had encountered this problem before and I guess I misread this output from the previous run. It seems whitespace is an issue but not dangling links. Disregard! /github/workspace/.refcache/reference.I-D.draft-birkholz-scitt-scrapi.xml: fetching from https://datatracker.ietf.org/doc/bibxml3/draft-birkholz-scitt-scrapi.xml
*** Can't get with persistent HTTP: Status code 404 while fetching https://datatracker.ietf.org/doc/bibxml3/draft-birkholz-scitt-scrapi.xml
*** 404 Not Found while fetching https://datatracker.ietf.org/doc/bibxml3/draft-birkholz-scitt-scrapi.xml
*** No such file or directory @ rb_sysopen - /github/workspace/.refcache/reference.I-D.draft-birkholz-scitt-scrapi.xml for /github/workspace/.refcache/reference.I-D.draft-birkholz-scitt-scrapi.xml |
|
@aj-stein-nist hmm, you are right... seems scrapi is not published well enough to be referenced... I will have to fix that, but apparently its not blocking the PR... which is weird. |
I too thought it was weird, I'll look into the i-d template action and consider if there is a bug to report or enhancement to file. |
|
PR against SCRAPI which can take some of these changes, but which I am intentionally leaving light. |
Signed-off-by: steve lasker <[email protected]>
|
fixes #117 |
Format and spellcheck fixes to #139
There was a problem hiding this comment.
LGTM
Per the editors call, there was a few open questions that @fournet was going to open new issues and prs for tracking.
This PR completes the previous decision to segment the APIs into: https://github.com/ietf-scitt/draft-birkholz-scitt-scrapi/
This PR removes implementation details from the architecture, many of which are specific to SCRAPI.