-
Notifications
You must be signed in to change notification settings - Fork 10
Conversation
Initial commit based on Harry's journal example. Only just started; lots of vestigial bits there still.
Do not merge yet. |
This is 35 phenotypes, each of which needs 18 lines of duplicated context. This makes the file giGANTIC. 632 lines. Are we sure about this? cc:@cmungall
Draft for merging to master
Create journal-example2-l1.yaml
I would be grateful if @cmungall and @pnrobinson could have a look at this draft. Cheers |
Hi Julie,
|
On 17 Feb 2016, at 22:30, Peter Robinson wrote:
Ultimately this shifts the complexity onto the software that produces And it's not much of a win if no one is hand-authoring these (we are
See #22 First we need a syntactic way of indicating that this identifier is Second we need to consider the use case of referencing across files,
Are we restricting this to humans? If not, we need to ensure the scheme see also #23
|
@pnrobinson Re: "Monarch IDs" do you mean we should not use something like PMC4498842#patient1 but instead use just "patient 1"? for his example @harryhoch had used "http://monarchinitiative.org/patient1" and that was consequently in the iteration 1 of my file, but long since overwritten (I agree this pattern invites all kinds of issues). |
I think something like PMC4498842#patient1 is fine (although I would standardise on PMIDs if possible). I think the version I was looking at still had the "http://monarchinitiative.org/patient1" in it! |
On 17 Feb 2016, at 23:14, Peter Robinson wrote:
Either way it should be a CURIE, so PMID:123456/patient1 or somesuch may |
Agreed on CURIE. Are you cool with a hash delim though? (precisely to sidestep resolution issues) |
I like the idea, good On 17 Feb 2016, at 23:37, Julie McMurry wrote:
|
Initial commit based on Harry's journal example. Only just started; lots of vestigial bits there still.