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

docid.type may be wrong #2

Open
strogonoff opened this issue Jan 26, 2022 · 3 comments
Open

docid.type may be wrong #2

strogonoff opened this issue Jan 26, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@strogonoff
Copy link

strogonoff commented Jan 26, 2022

In this case, W3C documents’ docid.type is IETF, but it probably this should be W3C. Even though docid.type does not reflect publisher but schema/namespace, it still seems inappropriate to use IETF.

https://github.com/ietf-ribose/relaton-data-misc/blob/2540405759186e98c902248a58c15e9c49b64b37/data/reference.W3C.CR-rdf-schema.yaml#L14-L19

@ronaldtse
Copy link

These are W3C bibliographic data as provided by IETF. These document identifiers are indeed assigned by IETF, not by W3C. Maybe this should be considered correct?

@strogonoff
Copy link
Author

Whether acceptable or not depends on semantics of docid.type, which are still unclear to me.

@strogonoff
Copy link
Author

According to Ronald’s comment on #5,

The publisher is not IETF.

@strogonoff strogonoff added the bug Something isn't working label Feb 17, 2022
@strogonoff strogonoff changed the title W3C documents published by IETF? Publisher is wrong Mar 21, 2022
@strogonoff strogonoff changed the title Publisher is wrong docid.type may be wrong Mar 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants