Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing epo:hasMainActivity for BT-610-Provider-Buyer #34

Open
cristianvasquez opened this issue Jul 8, 2024 · 2 comments
Open

Missing epo:hasMainActivity for BT-610-Provider-Buyer #34

cristianvasquez opened this issue Jul 8, 2024 · 2 comments
Assignees
Labels
clarification required Further information is requested for closure

Comments

@cristianvasquez
Copy link
Contributor

cristianvasquez commented Jul 8, 2024

The “Activity of the contracting entity” is still not converted for BT-610-Provider-Buyer

Examples: 130210-2024 and 130636

In the mappings there is a reference for BT-10-Procedure-Buyer and BT-610-Procedure-Buyer, but not for BT-610-Provider-Buyer

rdfs:label "BT-10-Procedure-Buyer" ;
rdfs:comment "Activity Authority" ;
rr:predicate epo:hasMainActivity ;
rdfs:label "BT-610-Procedure-Buyer" ;
rdfs:comment "ActivityEntity" ;
rr:predicate epo:hasMainActivity ;
@schivmeister
Copy link
Collaborator

Could you clarify what you mean by BT-610-Provider-Buyer? It would help if you can cite the SDK fields.json or another file with information on this field, as we were unable to locate it anywhere.

@cristianvasquez
Copy link
Contributor Author

cristianvasquez commented Jul 8, 2024

Dear @muricna,

Could you help me to find out what is a BT-610-Provider-Buyer?

Perhaps it was a typo and it was BT-610-Procedure-Buyer instead?

@schivmeister schivmeister added the clarification required Further information is requested for closure label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification required Further information is requested for closure
Projects
None yet
Development

No branches or pull requests

2 participants