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

Add prefix [m4i] #970

Closed
Zack-83 opened this issue Nov 1, 2023 · 10 comments · Fixed by #971
Closed

Add prefix [m4i] #970

Zack-83 opened this issue Nov 1, 2023 · 10 comments · Fixed by #971
Labels
New Used in combination with prefix, metaprefix, or collection for new entries Prefix

Comments

@Zack-83
Copy link
Contributor

Zack-83 commented Nov 1, 2023

Prefix

m4i

Name

Metadata4Ing

Homepage

https://w3id.org/nfdi4ing/metadata4ing/

Repository

https://git.rwth-aachen.de/nfdi4ing/metadata4ing/metadata4ing/

Description

The ontology Metadata4Ing is developed within the NFDI Consortium NFDI4Ing with the aim of providing a thorough framework for the semantic description of research data, with a particular focus on engineering sciences and neighbouring disciplines. This ontology allows a description of the whole data generation process (experiment, observation, simulation), embracing the object of investigation, all sample and data manipulation procedures, a summary of the data files and the information contained, and all personal and institutional roles. The subordinate classes and relations can be built according to the two principles of inheritance and modularity. "Inheritance" means that a subclass inherits all properties of its superordinate class, possibly adding some new ones. Modularity means that all expansions are independent of each other; this makes possible for instance to generate expanded ontologies for any possible combinations of method × object of research.

License

https://creativecommons.org/licenses/by/4.0/

Example Local Unique Identifier

Method

Regular Expression Pattern for Local Unique Identifier

^\w+$

URI Format String

http://w3id.org/nfdi4ing/metadata4ing#$1

Wikidata Property

Q111516803

Contributor Name

Metadata4Ing Workgroup

Contributor GitHub

@Zack-83

Contributor ORCiD

0000-0002-2239-3955

Contact Name

Giacomo Lanza

Contact ORCiD

0000-0002-2239-3955

Contact GitHub

@Zack-83

Contact Email

giacomo.lanza@ptb.de

Additional Comments

No response

@Zack-83 Zack-83 added New Used in combination with prefix, metaprefix, or collection for new entries Prefix labels Nov 1, 2023
@cthoyt
Copy link
Member

cthoyt commented Nov 1, 2023

Thanks @Zack-83! We’re not too keen on accepting three character prefixes due to the likelihood of collisions with other prefixes in other domains, so do you think we can directly use metadata4ing as the prefix instead?

@Zack-83
Copy link
Contributor Author

Zack-83 commented Nov 1, 2023

Thanks @cthoyt for the fast response! Actually the prefix has already been in use for one and a half year and is also "registered" on Prefix.cc (see https://prefix.cc/m4i).

I would like to involve in the discussion my co-authors @doigl, @SArndt-TIB, @JohannesLipp.

@cthoyt
Copy link
Member

cthoyt commented Nov 16, 2023

@Zack-83 is this developed using a github or other git repository? Can you please share the information on that?

@Zack-83
Copy link
Contributor Author

Zack-83 commented Nov 16, 2023

@Zack-83 is this developed using a github or other git repository? Can you please share the information on that?

Yes. I added it to the description above: https://git.rwth-aachen.de/nfdi4ing/metadata4ing/metadata4ing/

@cthoyt
Copy link
Member

cthoyt commented Nov 16, 2023

@Zack-83 thanks! Just fixing a CI issue then will merge this :)

cthoyt added a commit that referenced this issue Nov 16, 2023
Closes #970

---------

Co-authored-by: Zack-83 <Zack-83@users.noreply.github.com>
Co-authored-by: Charles Tapley Hoyt <cthoyt@gmail.com>
@Zack-83
Copy link
Contributor Author

Zack-83 commented Dec 20, 2023

Dear @cthoyt , we have some minimum corrections to our entry (full list of contributors, correct hosting institutions). Should I reopen #971 or create a new merge request?

@cthoyt
Copy link
Member

cthoyt commented Jan 3, 2024

hi @Zack-83 thanks for being patient over break! Please make a new PR.

Note that the contributor list on Bioregistry is for who made contributions to the Bioregistry record, not the resource the record describes.

@Zack-83
Copy link
Contributor Author

Zack-83 commented Jan 10, 2024

Many thanks @cthoyt . I will do it.
The entry on Bioregistries was mostly prepared by me (together with you), but the ontology is a collective work.
If from your point of view it is preferrable to have only one name under "Contributors", would it be possible to add more names under "Contact"?

@cthoyt
Copy link
Member

cthoyt commented Jan 10, 2024

@Zack-83 the job of the Bioregistry record is not to keep track of who contributes to the ontology. The Bioregistry record only keeps track of who contributes to the Bioregistry record (as this could be people who are not actually working on the resource the record describes). We keep exactly one primary contact person for each prefix - the job of this slot is not to be for credit, but rather to denote a primary responsible person to get in touch with when there are problems. This concept is derived from the OBO Principle on Locus of Authority (https://obofoundry.org/principles/fp-011-locus-of-authority.html) if you want to read more

@Zack-83
Copy link
Contributor Author

Zack-83 commented Jan 10, 2024

Fine. I created the new pull request #1022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Used in combination with prefix, metaprefix, or collection for new entries Prefix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants