W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > June 2018

Re: [dxwg] Profile negotiation [RPFN]

From: kcoyle via GitHub <sysbot+gh@w3.org>
Date: Thu, 21 Jun 2018 22:34:38 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-399264343-1529620477-sysbot+gh@w3.org>
Rob's example above is what I would call the output from a "cross-walk" - data is converted from some database or metadata schema to another, and these schemas, in some cases, may be application profiles depending on their contents and functionality. It isn't clear to me if every use of metadata is a profile, however, so referring to profiles in the conneg work may not meet our definition of "profile", which is not (AFAIK) "any metadata schema." And not including non-profile metadata schemas may not satisfy the needs of conneg. We are going to have to spend some time on definitions. Note that we have (so far) defined profiles as:

A <dfn>profile</dfn> is a named set of constraints on one or more identified base specifications,
      including the identification of any implementing subclasses of datatypes,
      semantic interpretations, vocabularies, options and parameters of those base specifications
necessary to accomplish a particular function.

I think this is more restrictive than "arbitrary metadata schema".

Wanting to serve the same data using a different metadata schema has the reputation of being lossy (in terms of absolute semantics). Rob says: "a different URI would mean a different concept." But I'm not so sure that we aren't talking about different concepts, although I realize that this becomes philosophical at a point. I believe this is what is bothering @agreiner. These are different datasets. That doesn't mean that you can't give an identifier to your data in all of its forms, but the same data served with different metadata schemas as a result of a conversion process is indeed a different dataset. But what is really troubling me is the use of "profile". 

(I know that "schema" isn't a great word to use here - substitute "model" or whatever you prefer if it bothers you.)

-- 
GitHub Notification of comment by kcoyle
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/74#issuecomment-399264343 using your GitHub account
Received on Thursday, 21 June 2018 22:34:41 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 October 2019 00:15:44 UTC