Re: Start of profiles analysis page - 2nd reply

OGC has been codifying profiles of XML based APis using Schematron

Here is an example (via a Linked Data interface we are starting to put over
these types of resources - for the reasons discussed in this email thread!)

http://www.opengis.net/def/profiles_example/wmts_simple

A few salient points here:

1) The profile is normatively a document, but it references a normative
machine-readable constraint expression that must be satisfied for
conformance
2) Profiles may reference as many such constraints
3) Different profiles may use different constraint languages
4) OGC has moved towards separating the information model for a
specification from one or more encoding specifications, and is increasingly
facing the need for profiles of aspects, which may have multiple encodings
(i.e. we need to express profile content independently of encoding (MIME
type)
5) we will definitely want to support text, Schematron and SHACL now and
unspecified options in the future
6) we can build services that implement negotiation mechanisms
7) in the backend we will support entailment rules - such as providing a
flattened view of profile hierarchies where the constrain language supports
this
8) we desire (and are willing co-design) a profiles expression language in
RDF that supports both hierarchical declaration and flattened views of
profiles that specify the underlying source of each constraint.

It would appear to me that every specification has an "identity profile" -
i.e. a possibly empty set of constraints. so "conformsTo" should work
equally well for specifications and profiles. so the challenge is how to
locate the possible machine readable resources?   At this point we are in
solution space...

What is the best way of having relevant machine readable resources
discoverable by machine, and relevant human readable resources discovered
via hypertext interaction?

is this analagous to Dataset/Distribution ?

Do we use simple Conneg to get versions of the profile using a specific
language - with the semantics that the constraints expressed are the subset
that can be expressed in this language?

Rob


On Mon, 11 Dec 2017 at 20:30 Karen Coyle <kcoyle@kcoyle.net> wrote:

>
>
> On 12/10/17 5:34 AM, Svensson, Lars wrote:
> > On Wednesday, December 06, 2017 11:44 PM, Karen Coyle [mailto:
> kcoyle@kcoyle.net] wrote:
> >
> >> On 12/6/17 2:28 PM, Ruben Verborgh wrote:
> >>>> Unfortunately, the majority case appears to be that profiles are not
> >>>> created by coders. A look at the current generation of profiles shows
> >>>> that they are Word or PDF documents, most likely written by folks who
> >>>> are knowledgeable of the semantics of their community's metadata but
> who
> >>>> do not themselves write code.
> >>>
> >>> They can keep on writing Word and PDF documents;
> >>> but we cannot expect all of them to write RDF documents.
> >>>
> >>> So they might be able to define profiles in human-readable ways,
> >>> but not necessarily the formal specifications to validate them.
> >>
> >> Actually,this is the advantage of CVSW - Most of them can understand and
> >> use spreadsheets, and from those spreadsheets the CVSW -> JSON-LD/RDF
> >> works. The idea is to give those folks a transitional technology, not to
> >> leave them in the dust. In my mind, these are the primary audience for
> >> application profiles.
> >
> > Is that the primary audience for reading or writing Aps?
>
> Perhaps not, but I'm not aware of anyone creating APs that are not in
> tabular form. If you know of any, please add them to the page:
>
> https://www.w3.org/2017/dxwg/wiki/ProfileContext
>
> kc
>
> >
> > And I think we should try not only to look at application profiles for
> data encoded in RDF, but also using other technologies (e. g. XML or
> perhaps even CSV [is it possible to have a profile for statistical data
> that specifies that e. g. every row is a day in a month (encoded using ISO
> format), the first column is precipitation in mm/m2, the second is
> temperature in degrees Celcius at 06:00, the third at 12:00 etc. so that
> applications will notice when the CSV format is changed?]).
> >>
> >> kc
> >>
> >>>
> >>> Best,
> >>>
> >>> Ruben
> >>>
> >>
> >> --
> >> Karen Coyle
> >> kcoyle@kcoyle.net http://kcoyle.net
> >> m: 1-510-435-8234 (Signal)
> >> skype: kcoylenet/+1-510-984-3600 <+1%20510-984-3600>
> >
>
> --
> Karen Coyle
> kcoyle@kcoyle.net http://kcoyle.net
> m: 1-510-435-8234 (Signal)
> skype: kcoylenet/+1-510-984-3600 <+1%20510-984-3600>
>
>