search

ec-geolink / design

Design information about the EarthCube Geolink project.
8 stars 1 forks source link

Develop proposal for DataOne people/org URI service #48

Open amoeba opened 9 years ago

amoeba commented 9 years ago
amoeba commented 9 years ago

First draft of proposal at https://github.com/ec-geolink/design/blob/d1-people/data/dataone/people/proposal.md (versioned link)

amoeba commented 9 years ago

Made some changes after feedback from an nceas-dev call.

https://github.com/ec-geolink/design/commit/36c4609b3f5378df63cb3da0fd1de186fda8a281#diff-85add793ea976a429e22369145d91a9c

amoeba commented 9 years ago

I'll close this issue now as the proposal has been created, feedback has been obtained, and revisions have been made. The document is a live document however.

bob-arko commented 9 years ago

One quick thought. I would use a dedicated third-level domain for your Linked Data URIs. One popular style is "data.".

For example: data.nytimes.com data.rvdata.us data.geolink.org

So instead of this: http://dataone.org/people/brycemecum I would use: http://data.dataone.org/people/brycemecum

On Tue, Sep 01, 2015 at 02:55:36PM -0700, Bryce Mecum wrote:

Made some changes after feedback from an nceas-dev call.

https://github.com/ec-geolink/design/commit/36c4609b3f5378df63cb3da0fd1de186fda8a281#diff-85add793ea976a429e22369145d91a9c

amoeba commented 9 years ago

Good idea on the data URIs.

Matt and I had a good work session on this proposal yesterday and I'll be updating the proposal substantially with the results of our work. In its current state, I think the proposal is too vague and doesn't explain enough about what we are doing at NCEAS with authenticated accounts and how we are dove-tailing that with what we're doing with our GeoLink LOD datasets graph. Hopefully my changes will explain this more clearly.

amoeba commented 9 years ago

Note for myself: I would like to expand the writeup of this with diagram, like what's at https://releases.dataone.org/online/api-documentation-v1.2.0/design/SearchMetadata.html, to better explain how the pieces of the service work together and are related to one another.