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

Meaning of identifierSpace and schemaSpace #3

Closed
wetneb opened this issue Sep 24, 2019 · 2 comments · Fixed by #76
Closed

Meaning of identifierSpace and schemaSpace #3

wetneb opened this issue Sep 24, 2019 · 2 comments · Fixed by #76

Comments

@wetneb
Copy link
Member

wetneb commented Sep 24, 2019

I am not sure how to define the identifierSpace and schemaSpace parameters so I have started a discussion about this in the group:
https://lists.w3.org/Archives/Public/public-reconciliation/2019Sep/0001.html

@wetneb
Copy link
Member Author

wetneb commented Dec 14, 2019

This was written up in the specs.

@acka47
Copy link
Member

acka47 commented Oct 26, 2021

Reopening, see hbz/lobid-gnd#296 (comment).

@acka47 acka47 reopened this Oct 26, 2021
fsteeg added a commit that referenced this issue Nov 16, 2021
Joining suggestions by Adrian and Thad, tweaked for consistency

Co-authored-by: Adrian Pohl <pohl@hbz-nrw.de>
Co-authored-by: Thad Guidry <thadguidry@gmail.com>
wetneb pushed a commit that referenced this issue Nov 16, 2021
* Adjust definition of schema space (#3)

based on https://lists.w3.org/Archives/Public/public-reconciliation/2019Oct/0002.html,
bumped by discussion in hbz/lobid-gnd#296.

* Adjust definitions of identifier and schema space (#3, #76)

Joining suggestions by Adrian and Thad, tweaked for consistency

Co-authored-by: Adrian Pohl <pohl@hbz-nrw.de>
Co-authored-by: Thad Guidry <thadguidry@gmail.com>

Co-authored-by: Fabian Steeg <steeg@hbz-nrw.de>
Co-authored-by: Thad Guidry <thadguidry@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants