Move to full MyCapytain DTS compliance

[sonofmun]

This issue is to track what needs to be changed to make HookTest compliant with the new MyCapytain guidelines: https://github.com/Capitains/guidelines. The user will be able to choose whether to use these new guidelines or the old guidelines through the guidelines parameter, i.e., choosing 3.epidoc or 3.tei instead of 2.epidoc or 2.tei. Changes that I see right now need to be made:

• [ ] HookTest should use the new __capitains__.xml files instead of __cts__.xml
  • This will require a change to the finder, probably with a new DTSFinder sub-class (see https://github.com/Capitains/HookTest/blob/c695aadb65e2592d5b0fb7feee3013fdfbda8449/HookTest/test.py#L30-L94)
  • It will also require code to correctly test these files, probably as a DTSMetadata_TestUnit sub-class of TESTUnit
• [ ] Compatible with new text guidelines
  • According to the guidelines, the only changes here are in the refsDecl. Here we need to:
  • [ ] Check the @n and @xml:base attributes on the refsDecl element
  • [ ] Check the @corresp attribute on cRefPattern to make sure it exists and there are no duplicates. Perhaps also that every level has a cRefPattern, i.e., that the number of cRefPattern nodes equals the max depth of a citation in the text.
  • [ ] Check the @matchPattern attributes on cRefPattern to make sure that:
  • [ ] they are unique
  • [ ] that the number of dots in the @matchPattern == @corresp - 1. This should help to avoid the error of using dot to match all and that the @matchPattern is for a different citation level than the one being represented.

What have I forgotten here?

[ThomasK81]

Hi, does this mean that it does not accept __cts__.xml anymore? IF so, a heads-up would have been nice. We might move to an older hook version if that is the case.

[PonteIneptique]

Can't be, nothing was merged, nothing was completed afaik. And your repository fails also with 1.2.5 and MyCapytain 2.0.10. You should create a new issue, this is definitely unrelated.

Btw, you should not worry regarding versioning, if you check for not installing past major version ("<2.0.0") the CLI should not have breaking features. ;)

[PonteIneptique]

And 3.0.0 will keep compatibility with previous __cts__.xml.

[ThomasK81]

Thanks for the quick reply. I will do some more trouble-shooting on our end and then file a new issue if needed. :)