You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However this only works for non composites, since composites can have more than one text element, each having it's own PROJECT token.
I haven't looked through the whole corpus but had a look at several of the composites and all the texts inside seem to belong to the same project.
When sending the SOAP envelope for the validation, one project name needs to be specified, so it makes sense it is unique through the file, although it doesn't make sense the original ORACC grammar includes the PROJECT token in all elements of a composite if it's going to be the same.
Need to clarify this with Steve/Eleanor to make sure the contents of the soap envelope are correct.
The text was updated successfully, but these errors were encountered:
This is not actually an issue as such but a misunderstanding of terms
Composites are marked with @composite and only contains one project line the files
with more than one project line are a gathering of small files. And they always have the same project. See #51 @raquel-ucl I think this can close?
Nammu needs to read the project from a parsed ATF. The way it was doing it so far was like this:
However this only works for non composites, since composites can have more than one text element, each having it's own PROJECT token.
I haven't looked through the whole corpus but had a look at several of the composites and all the texts inside seem to belong to the same project.
When sending the SOAP envelope for the validation, one project name needs to be specified, so it makes sense it is unique through the file, although it doesn't make sense the original ORACC grammar includes the PROJECT token in all elements of a composite if it's going to be the same.
Need to clarify this with Steve/Eleanor to make sure the contents of the soap envelope are correct.
The text was updated successfully, but these errors were encountered: