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

BPs 2 and 22 are duplicates #100

Closed
lvdbrink opened this issue Dec 10, 2015 · 3 comments
Closed

BPs 2 and 22 are duplicates #100

lvdbrink opened this issue Dec 10, 2015 · 3 comments
Assignees

Comments

@lvdbrink
Copy link
Contributor

Our Best Practice 2: Reuse existing (authoritative) identifiers when available looks like it could be a duplicatie of Best Practice 22: Link to resources with well-known or authoritative identifiers.

The first is in the Assigning identifiers section, the second in Linking spatial data. I added content to the first one today. Please check whether they are duplicates and if BP 2 content should be moved to BP 22, and removed.

@6a6d74
Copy link
Contributor

6a6d74 commented Dec 10, 2015

Hi @lvdbrink ... I don't think they're duplicates. My thought is as follows:

BP2 is about assignment of an identifier to the thing you're interested in publishing.
BP22 is about relating your thing to other things with well-known identifiers ... for example, during our f2f we talked about relating Surrey University to Guildford [http://sws.geonames.org/2647793].

Clearly these are related. We should identify the related nature of these BPs within the doc.

@lvdbrink
Copy link
Contributor Author

Okay, clear. Part of the text of BP2 could then very well be a better fit for BP22. Please cut&past whatever is appropriate. I added a reference to BP22 and this issue to the text of BP2.

lvdbrink added a commit that referenced this issue Dec 10, 2015
@lvdbrink
Copy link
Contributor Author

No longer relevant because of document restructuring. Partly now in BP7 and partly in BP14.

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

No branches or pull requests

2 participants