- From: Thad Guidry <thadguidry@gmail.com>
- Date: Mon, 30 Sep 2019 12:09:13 -0500
- To: David Newbury <DNewbury@getty.edu>
- Cc: David Huynh <dfhuynh@gmail.com>, Antonin Delpeuch <antonin@delpeuch.eu>, "public-reconciliation@w3.org" <public-reconciliation@w3.org>
- Message-ID: <CAChbWaP_mP9phsgD1JaHtdPvpUf1dm4aqHYvMo9szbjSAzRJ5g@mail.gmail.com>
Hi David Newbury, OpenRefine does not process these IDs currently. But users are certainly able to do things with the fields, even if they manually form GET requests to Recon endpoints. I am not sure how much metadata is exposed currently that users are able to interact with in OpenRefine for Recon services. "cell" in a Recon object shows all the fields currently exposed. Perhaps Antonin can summarize that for us. The idea of the IDs for these 2 fields is that the IDs sometimes hold information...like metadata in a way. They become useful I would say for collaborative efforts sometimes, as is often the case with Linked Data. Bits of info and hints of categories, domains, general classifications sometimes show up in those URI or IDs, as they did with Freebase in particular. My definitions for these 2 fields in Reconciliation API would begin to look like this... schemaSpace : A URI or ID that represents a group of entities by some Domain or Schema, ex: "/usa/people/person", or "006_electronic_journals" or simply "football" identifierSpace: A URI or ID that represents a group??? of entities by some ??? Thad https://www.linkedin.com/in/thadguidry/ On Mon, Sep 30, 2019 at 10:26 AM David Newbury <DNewbury@getty.edu> wrote: > Hi all—been lurking here a bit and have been encouraged to jump in and > participate. > > > > I agree with the “Why” question. At the Getty, we’re using links to our > documentation for our URL structure and our type structure, but that’s > pretty arbitrary. (Our enpoint is at > http://services.getty.edu/vocab/reconcile). We had a discussion about > what to put there, and in the absence of a rationale, we put what we > thought would be most helpful to a user trying to understand our schema > space. > > > > The questions I would ask, to help understand what goes here would be: > Does OpenRefine actually process these IDs in any way? Are we aware of any > client that does? And is the point here to just provide data hooks for > extensibility, or is there anything else it does? > > > > > > > > — David > > > > David Newbury > > Enterprise Software Architect, Getty Digital > > > > Email: dnewbury@getty.edu > > Phone: (310) 440-6116 > > > >
Received on Monday, 30 September 2019 17:09:49 UTC