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.

Sign up for GitHub

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

Jump to bottom

Formalize project exit criteria (definition of done) #10

Open
nissimsan opened this issue Jan 9, 2022 · 7 comments
Open

Formalize project exit criteria (definition of done) #10

nissimsan opened this issue Jan 9, 2022 · 7 comments
Assignees
@kevinbish
Labels
documentation Improvements or additions to documentation

Comments

@nissimsan
Copy link
Contributor

No description provided.

@nissimsan
Copy link
Contributor Author

@kevinbish

@nissimsan
Copy link
Contributor Author

@kevinbish , gentle poke on this, pls?

@onthebreeze
Copy link
Contributor

A published vocabulary
An architecture & governance model for vocabulary management and context files

@nissimsan
Copy link
Contributor Author

@kevinbish you think you'll get around to this?

@kevinbish
Copy link
Contributor

kevinbish commented May 6, 2022 •
edited
Loading

@kevinbish you think you'll get around to this?

Ideally, as @onthebreeze said the main outcome of this project exit will be a (fully-officially) published vocabulary. Not a draft :)

_On a side note: But I am also mindful that there needs to be an overall strategy for the Vocab and API management. I have been in discussion with the Bureau on this; Chair Sue and VC Marek, as well as the Lib Maint Team and another API tech Spec Project about this to formulate a strategy that defines the governance of the UN/CEFACT API/JSON-LD artefacts. The Bureau indicated that they will form a team of specialists/group around this; but I have not seem any action as yet.

We will need to have an overall strategy for the publication rules/process and governance of these new outputs._

@nissimsan
Copy link
Contributor Author

@kevinbish, if you could please submit a PR which just address the topic of the issue, that'd be awesome. Cheers!

@cmsdroff cmsdroff added the documentation Improvements or additions to documentation label Jun 10, 2022
cmsdroff added a commit that referenced this issue Jun 10, 2022
@cmsdroff
Exit Criteria Mod
e89822a 
Related to #10 adding the publication of a official json-ld on UNECE site.
@cmsdroff
Copy link
Contributor

cmsdroff commented Jun 10, 2022 •
edited
Loading

@kevinbish ive updated the https://github.com/uncefact/vocab/blob/cmsdroff-docs-changes/docs/tech-spec.md to reflect this.

Also the discussion that you mentioned

_On a side note: But I am also mindful that there needs to be an overall strategy for the Vocab and API management. I have been in discussion with the Bureau on this; Chair Sue and VC Marek, as well as the Lib Maint Team and another API tech Spec Project about this to formulate a strategy that defines the governance of the UN/CEFACT API/JSON-LD artefacts. The Bureau indicated that they will form a team of specialists/group around this; but I have not seem any action as yet.

This is related to (in my opinion) to #87 and suggest we have any further conversation over there about this.

anything else we need to do or can we close this ticket?

@cmsdroff cmsdroff mentioned this issue Jun 10, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kevinbish kevinbish

Labels
documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@cmsdroff @onthebreeze @nissimsan @kevinbish