Repository navigation
Add gleaner @ids for organizations and other blank nodes (#21) - #35
Conversation
fils
left a comment
There was a problem hiding this comment.
Actually, there is a best practice we should be following here..
https://example.org/.well-known/genid/
so for us
https://gleaner.io/.well-known/genid/
after genid/ we can do anything we want to something like
https://gleaner.io/.well-known/genid/xid/person/c-hari is fine, though xid seems redundant then.
ref: https://www.w3.org/TR/rdf12-concepts/#section-skolemization
c206049 to
5c20d00
Compare
Good call. Updated the blank-node ids to Skolem IRIs and dropped the extra
The WebPage and DataCatalog ids from #19 are still |
|
remembering xid was supposed to be a repository code so some future URL resolver could resolve a uri: aka eco or earthcube
|
|
You're right. I treated The CHELSA WebPage and DataCatalog ids still use the literal
Which repository code should this collection use in that slot, |
|
lets go with earthcube, no use using the EarthCube Office (eco)
|
Switched the CHELSA WebPage and DataCatalog ids to the
The WebPage |
Summary
@idwhen they do not already have one:https://gleaner.io/xid/{type}/{host/path}fromurl, otherwise a name slug.sameAs) orurlfor Dataset, ScholarlyArticle, and CreativeWork. Point a one-dataset folder's WebPageabout/mainEntityat that dataset file's@id.scripts/generate_jsonld.pyand document it in the JSON-LD prompt. Leave the ChatGPTsdPublishernode for AI: add (at)id to sdPublisher #20.Test plan
webpage.jsonldpublisher@idishttps://gleaner.io/xid/organization/www.wsl.ch/en/index.html@id(MRLC publisherhttps://www.mrlc.gov/#org) is unchangedabout/mainEntitymatches that dataset file's@id(for example G-RUN)sameAsas@idsdPublisherstill has no@id