Submissions:ProposeCP

From Odp

(Difference between revisions)
Jump to: navigation, search
Current revision (08:40, 12 October 2009) (view source)
 
(25 intermediate revisions not shown.)
Line 1: Line 1:
{{#ifLogged:
{{#ifLogged:
-
{{Info tip| What is the procedure for posting a Content Ontology Design Pattern proposal?}}
+
{{Propose a pattern
 +
|Image=HelpPattern.png
 +
|Info=
 +
* Check if the domain of your Content ODP is in the [[Community:Domain| list of domains]], otherwise [[Community:Domain| create it]]
 +
* [[Special:Upload|Upload the image]] with a diagrammatic view of your pattern
 +
* '''If you have already an OWL file you can create a page directly [[Special:ImportProposal| by importing it]]'''
 +
* If you don't have and OWL file yet you should {{#formlink:Content_OP_Proposal_Form|create a page by filling a form|link|}}
 +
* Edit the page to fill all the necessary information by clicking on the ''edit'' button on the top of your CP page
-
=== Step 1: Is the domain of your Content OP already in this [[Community:Domain| list of domains]]?  ===
+
}}
-
* Yes: go to Step 2
+
{{Info tip| If you are not aware of the recommended procedure for posting a Content Ontology Design Pattern proposal, the five steps are described below.}}
-
* No: create a page for it before continuing from [[Community:Domain| the page of domains]]
+
-
=== Step 2: Do you have a picture depicting a diagrammatic view of your Content OP? ===
+
__NOTOC__
-
* Yes: [[Special:Upload| upload it]] and remember the name of the picture file
+
== Recommended Procedure for Posting Content OP proposals ==
-
* No: it is recommended to have include it in the Content OP page. For Content OP certification it is required
+
-
=== Step 3: Do you have the owl file of your pattern? ===  
+
=== Step 1: Is the domain of your Content OP already in the [[Community:Domain| list of domains]]? ===
-
* Yes
+
* Yes? Go to Step 2
-
** Download the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl CP annotation schema]
+
* No? Create a page for it, from [[Community:Domain| the page of domains]], before continuing.
-
** Import the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl CP annotation schema] in the owl file of the Content OP
+
-
** Annotate the Content OP by using rdfs:label, rdfs:comment, and the CP annotation schema annotation properties in order to comment the Content OP (intent, consequences, scenarios, etc.)
+
-
** Put the Content OP owl file on a server, assign a [http://www.w3.org/Provider/Style/URI cool URI] to it. You will indicate such URI to the automatic import service, and will also be the value you will put in the "OWL building block" field/property
+
-
** Go to [[Special:ImportProposal| import CP]]
+
-
*** Type the name for the page of your proposed Content OP
+
-
*** Indicate the URI of the owl file encoding the Content OP
+
-
*** Click on "load"
+
-
** Go to Step 4
+
-
* No
+
=== Step 2: Do you have a picture showing a diagrammatic view of your Content OP? ===
-
** Type the name for the page of your proposed Content OP in the form below and click on "create"
+
-
*** Note: if a page with that name already exists, you will be directed to editing that page
+
-
{{#forminput:Content_OP_Proposal_Form|25||create|namespace=Submissions}}
+
* Yes? [[Special:Upload| Upload it]] and remember the name of the picture file.
-
|{{Not allowed|Action=propose a Content OP}}
+
* No? It is recommended to include a picture in every Content OP proposal. It is required before your Content OP can be certified.
-
}}
+
-
* Fill the form
+
=== Step 3: Do you have the owl file of your pattern? ===
-
* Save the Content OP proposal page
+
 
-
* Encode your Content OP in an owl file and include the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl CP annotation schema]
+
* Yes?
 +
** Download the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl CP annotation schema].
 +
** Import the [http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl CP annotation schema] into the OWL-file containing the Content OP.
 +
** Annotate the Content OP by using rdfs:label, rdfs:comment, and the CP annotation schema annotation properties in order to comment the Content OP, i.e. describing its intent, consequences, scenarios, etc. The properties in the CP annotation schema are in themselves commented, be sure to read and understand the meaning of the properties before annotating.
 +
** Put the Content OP OWL-file on a server, i.e. accessible over the Internet, and assign a [http://www.w3.org/Provider/Style/URI cool URI] to it. This URI you will provide to the automatic import service when submitting the pattern, and it will also be the value of the "OWL building block" field/property when you edit the proposal page (see Step 4).
 +
** Go to the [[Special:ImportProposal| import CP]] page.
 +
*** Type the name of the page you want to create for your proposed Content OP, preferably this should coincide with the name of the pattern.
 +
*** Indicate the URI of the OWL-file encoding the Content OP that you created (see above).
 +
*** Click on "load".
 +
** Go to Step 4
 +
 
 +
* No?
 +
** At the moment only OWL representation of patterns is supported. Please create an OWL-file and return to Step 3.
=== Step 4: Editing the Content OP proposal page ===
=== Step 4: Editing the Content OP proposal page ===
-
* Edit the Content OP page you just created  
+
* Edit the Content OP page you just created, i.e. go to the page and choose "edit".
-
* Indicate the domain of your Content OP in the appropriate field
+
* Indicate the domain of your Content OP in the appropriate field.
-
* Indicate the name of the diagram picture (including its extension) in the appropriate field
+
* Indicate the file name of the diagram picture (including its extension) in the appropriate field.
-
* Indicate all possible relations with other Content OP by linking to their pages from the appropriate fields
+
* Indicate all possible relations to other Content OP by linking to their pages from the appropriate fields.
-
* Indicate the URI of the owl file encoding the Content OP in the appropriate field
+
* Indicate the URI of the OWL-file encoding the Content OP in the appropriate field.
-
* Save the Content OP proposal page
+
* Save the Content OP proposal page.
=== Step 5: Review ===
=== Step 5: Review ===
-
* Ask for a review of your Content OP by clicking on "ask for a review" on top of the proposal page
+
* Ask for a review of your Content OP by clicking on "ask for a review" at the top of the proposal page.
 +
 
 +
|{{Not allowed|Action=propose a Content OP}}
 +
}}

Current revision

Sorry, you need to be logged to propose a Content OP.

If you don't have an ODP account, you can request it.

Personal tools
Quality Committee
Content OP publishers