W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > February 2020

Re: [dxwg] Values for dcterms:conformsTo of instances dcat:DataService (sparql endpoints, for example) (#1211)

From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
Date: Wed, 19 Feb 2020 23:18:21 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-588524779-1582154300-sysbot+gh@w3.org>
@nicholascar has pointed out that this use case is a motivation for the Profiles Vocabulary as an information resource that can address such Use Cases. Its worth pointing out that implicit in this is the HTTP-range14 problem - you need to reference the conceptual specification as @dr-shorthair suggested - and then decide what information resource it best has.  

When you are talking about "schema" - thats a perfect example of where flexibility is needed for different resources that form part of the recipe for a specification. For XML that will be XSD, for JSON that will be JSON-schema, for RDF its RDFS, OWL and/or SHACL.  But if using JSON you also might want JSON-LD contexts. 

At this point you can both describe all the available resources using Profiles - but you can also dereference specification URI using content-negotiation and content-negotiation-by-profile to access resources directly without processing the prof description. 

Ultimately you need a framework for disseminating the identifiers to the community - having a URL link to some information resource is inherently fragile and non-extensible, so you need to manage non-information-resource URIs and infrastructure to dereference these. 

At the OGC I am working through publishing profile descriptions for specifications, and setting up such infrastructure - but there is a legacy of embedded document references to think about too.

Some members of the DXWG are interested in best practices for publishing specifications from a practical sense, but whether this emerges as a formal deliverable in some guidance document is not clear yet. Please include us in reviews of any proposals to formalise requirements.

-- 
GitHub Notification of comment by rob-metalinkage
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1211#issuecomment-588524779 using your GitHub account
Received on Wednesday, 19 February 2020 23:18:23 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:34 UTC