Line 5: Line 5:
 
|Info=
 
|Info=
  
* [[Special:Upload|Upload the image]] with a diagrammatic view of your pattern  
+
* [[Special:Upload|Upload the image]] with a graphical representation of the generic non-ontological resource to be re-engineered
 +
* [[Special:Upload|Upload the image]] with a graphical representation of the generated ontology
 +
* [[Special:Upload|Upload the image]] with a diagrammatic view of your pattern, the set of steps to perform the transformation
 +
* [[Special:Upload|Upload the image]] with a graphical representation of an example of the non-ontological resource to be re-engineered
 +
* [[Special:Upload|Upload the image]] with a graphical representation of an example of the generated ontology
 +
* [[Special:Upload|Upload the image]] with a diagrammatic view of your pattern, the set of steps to perform the transformation for the example
 
* {{#formlink:Reengineering_OP_Proposal_Form|Create the page by filling a form|link|}}
 
* {{#formlink:Reengineering_OP_Proposal_Form|Create the page by filling a form|link|}}
 
* Edit the page to complete all the necessary information by clicking on the ''edit'' button on the top of your pattern page, also remember to ask for a review of your pattern or indicate if you are submitting for a specific event
 
* Edit the page to complete all the necessary information by clicking on the ''edit'' button on the top of your pattern page, also remember to ask for a review of your pattern or indicate if you are submitting for a specific event
 
+
* Note.- Recommended picture size at 300 x 460, or less.
  
 
}}
 
}}
Line 18: Line 23:
 
== Recommended Procedure for Posting Reengineering ODP proposals ==  
 
== Recommended Procedure for Posting Reengineering ODP proposals ==  
  
=== Step 1: Do you have a picture showing a diagrammatic view of your Reengineering ODP? ===
+
=== Step 1: Do you have a graphical representation of the generic non-ontological resource to be re-engineered? ===
 +
 
 +
* Yes? [[Special:Upload| Upload it]] and remember the name of the picture file.
 +
* No? It is recommended to include a picture in every proposal.
 +
 
 +
=== Step 2: Do you have a graphical representation of the generated ontology? ===
 +
 
 +
* Yes? [[Special:Upload| Upload it]] and remember the name of the picture file.
 +
* No? It is recommended to include a picture in every proposal.
 +
 
 +
=== Step 3: Do you have a graphical diagrammatic view of your pattern, the set of steps to perform the transformation? ===
 +
 
 +
* Yes? [[Special:Upload| Upload it]] and remember the name of the picture file.
 +
* No? It is recommended to include a picture in every proposal.
 +
 
 +
=== Step 4: Do you have a graphical representation of an example of the non-ontological resource to be re-engineered? ===
 +
 
 +
* Yes? [[Special:Upload| Upload it]] and remember the name of the picture file.
 +
* No? It is recommended to include a picture in every proposal.
 +
 
 +
=== Step 5: Do you have a graphical representation of an example of the generated ontology? ===
 +
 
 +
* Yes? [[Special:Upload| Upload it]] and remember the name of the picture file.
 +
* No? It is recommended to include a picture in every proposal.
 +
 
 +
=== Step 6: Do you have a diagrammatic view of your pattern, the set of steps to perform the transformation for the example? ===
  
 
* Yes? [[Special:Upload| Upload it]] and remember the name of the picture file.
 
* Yes? [[Special:Upload| Upload it]] and remember the name of the picture file.
 
* No? It is recommended to include a picture in every proposal.
 
* No? It is recommended to include a picture in every proposal.
  
=== Step 2: Create the page of the new pattern ===  
+
=== Step 7: Create the page of the new pattern ===  
  
 
* {{#formlink:Reengineering_OP_Proposal_Form|Create the page by filling out this form|link|}}
 
* {{#formlink:Reengineering_OP_Proposal_Form|Create the page by filling out this form|link|}}
  
=== Step 3: Editing the Reengineering ODP proposal page ===
+
=== Step 8: Editing the Reengineering ODP proposal page ===
  
 
* Edit the pattern page you just created, i.e. go to the page and choose "edit" in the menu at the top.  
 
* Edit the pattern page you just created, i.e. go to the page and choose "edit" in the menu at the top.  
Line 36: Line 66:
 
* Save the Reengineering ODP proposal page.
 
* Save the Reengineering ODP proposal page.
  
=== Step 4: Review ===
+
=== Step 9: Review ===
  
 
* Ask for a review of your Reengineering ODP by clicking on "ask for a review" at the top of the proposal page.
 
* Ask for a review of your Reengineering ODP by clicking on "ask for a review" at the top of the proposal page.

Latest revision as of 00:42, 6 August 2009

{{#ifLogged:


How to propose a pattern (in a nutshell)
HelpPattern.png
  • Upload the image with a graphical representation of the generic non-ontological resource to be re-engineered
  • Upload the image with a graphical representation of the generated ontology
  • Upload the image with a diagrammatic view of your pattern, the set of steps to perform the transformation
  • Upload the image with a graphical representation of an example of the non-ontological resource to be re-engineered
  • Upload the image with a graphical representation of an example of the generated ontology
  • Upload the image with a diagrammatic view of your pattern, the set of steps to perform the transformation for the example
  • Edit the page to complete all the necessary information by clicking on the edit button on the top of your pattern page, also remember to ask for a review of your pattern or indicate if you are submitting for a specific event
  • Note.- Recommended picture size at 300 x 460, or less.


Info tip.gif If you are not aware of the recommended procedure for posting a Reengineering Ontology Design Pattern proposal, the four steps are described below.


Recommended Procedure for Posting Reengineering ODP proposals

Step 1: Do you have a graphical representation of the generic non-ontological resource to be re-engineered?

  • Yes? Upload it and remember the name of the picture file.
  • No? It is recommended to include a picture in every proposal.

Step 2: Do you have a graphical representation of the generated ontology?

  • Yes? Upload it and remember the name of the picture file.
  • No? It is recommended to include a picture in every proposal.

Step 3: Do you have a graphical diagrammatic view of your pattern, the set of steps to perform the transformation?

  • Yes? Upload it and remember the name of the picture file.
  • No? It is recommended to include a picture in every proposal.

Step 4: Do you have a graphical representation of an example of the non-ontological resource to be re-engineered?

  • Yes? Upload it and remember the name of the picture file.
  • No? It is recommended to include a picture in every proposal.

Step 5: Do you have a graphical representation of an example of the generated ontology?

  • Yes? Upload it and remember the name of the picture file.
  • No? It is recommended to include a picture in every proposal.

Step 6: Do you have a diagrammatic view of your pattern, the set of steps to perform the transformation for the example?

  • Yes? Upload it and remember the name of the picture file.
  • No? It is recommended to include a picture in every proposal.

Step 7: Create the page of the new pattern

Step 8: Editing the Reengineering ODP proposal page

  • Edit the pattern page you just created, i.e. go to the page and choose "edit" in the menu at the top.
  • Indicate the file name of the diagram picture (including its extension) in the appropriate field.
  • Indicate all possible relations to other patterns by linking to their pages from the appropriate fields.
  • Fill out as many of the fields as possible.
  • Remember to indicate if you are submitting for a specific event.
  • Save the Reengineering ODP proposal page.

Step 9: Review

  • Ask for a review of your Reengineering ODP by clicking on "ask for a review" at the top of the proposal page.

| Sorry, you need to be logged to propose a reengineering pattern.

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

}}

The page [[Bootstrap:Footer]] was not found.