Vote on resolution to Issue

Ivan,

I had to leave the call before the vote on issue #329.  Please record my vote as a “-1”.

Reason:  The justification for not addressed this change is not based on whether this is an actual problem – it is strictly one of timing.  While not the intent of the working group, this places them in the role of “URL Police”.   We are telling two large bioinformatics communities (OBO and Prefixcommons) that this is their problem because a) they aren’t using prefixes the way that we had intended and b) it took them too long to discover and report the problem.  They now understand that JSON-LD 1.0 cannot address their issues – were it not for the upcoming 1.1 specification, they would have to give up on JSON-LD completely. We are about to release a standard that, while providing a work-around, still forces them to change their libraries, tools, documentation, and content.  It doesn’t help to tell them that we recognize that this is a problem and that a solution may be forthcoming at a later time – they still have to absorb the cost today if they wish to continue down the JSON-LD path.

Not a position that I’m anxious to defend.

Harold Solbrig
Assistant Professor
Johns Hopkins University | Division of  General Internal Medicine
2024 E Monument St | Suite 1-200 | Baltimore, MD 21287
+1 (507) 319-2628  | solbrig@jhu.edu<mailto:solbrig@jhu.edu>