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

[dxwg] profileDesc and the Guidance document

From: kcoyle via GitHub <sysbot+gh@w3.org>
Date: Fri, 25 May 2018 06:05:06 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-326392321-1527228295-sysbot+gh@w3.org>
kcoyle has just created a new issue for https://github.com/w3c/dxwg:

== profileDesc and the Guidance document ==
There are two possible approaches we can take to integrating profileDesc into our second deliverable. First would be a small-ish modification to the outline proposed by Lars. A W3C-structured document would exist as a separate item, not on recommendation track. (I'm not sure what options there are for a non-recommendation ontology, but I believe they do exist.)

* Introduction (non-normative)
* Definitions
    * Profile
    * Schema
    * Formalism
    * ...
* Profile description
    * This is the meat of the document. Important parts are:
        * A profile MUST have URI (or an IRI?) identifying it. The URI SHOULD be an http URI
        * A profile SHOULD have a title
        * A profile SHOULD have a textual description intended for humans
        * A profile's description MAY be expressed using a formal model we define (such as @rob-metalinkage 's proposal)
        * A profile document SHOULD link to schemas implementing the profile it describes
* Examples (non-normative)
    * ODRL is a good example since their profiles are explicitly media-type independent
* _Profile Description Ontology (non-normative)_
    * Introduction with link to PD documentation that exists elsewhere
    * Examples
* Bibliography

In the other option, profileDesc *is* the main normative content of the Guidance document. This could be seen to fit the definition of the Guidance deliverable, which is:
     A definition of what is meant by an application profile and an explanation of one or more methods for publishing and sharing them.
One could read this as meeting this outline:

* Introduction (non-normative)
  * What is a profile
        * A profile MUST have URI (or an IRI?) identifying it. The URI SHOULD be an http URI
        * A profile SHOULD have a title
        * A profile SHOULD have a textual description intended for humans
        * A profile's description MAY be expressed using a formal model we define (such as @rob-metalinkage 's proposal)
        * A profile document SHOULD link to schemas implementing the profile it describes
  * Examples (non-normative)
       * ODRL is a good example since their profiles are explicitly media-type independent
* Definitions
    * Profile
    * Schema
    * Formalism
    * ...
* Profile description ontology (normative)
    * This is the meat of the document
      * Background
      * Design rationale
      * (primary classes, definition of properties, etc. cf. [SKOS document](https://www.w3.org/TR/2009/REC-skos-reference-20090818/))
* Bibliography

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/242 using your GitHub account
Received on Friday, 25 May 2018 06:05:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 25 March 2019 10:33:23 UTC