http -> https

127e90fb · Project Open · e8ee303d · 127e90fb · 127e90fb · 127e90fb
Commit 127e90fb authored Feb 19, 2021 by Project Open
19 changed files
--- a/README.md
+++ b/README.md
--- a/acs-workflow.info
+++ b/acs-workflow.info
 <?xml version="1.0"?>
 <!-- Generated by the OpenACS Package Manager -->

-<package key="acs-workflow" url="http://www.arsdigita.com/acs-repository/apm/packages/acs-workflow/" type="apm_application">
+<package key="acs-workflow" url="https://www.arsdigita.com/acs-repository/apm/packages/acs-workflow/" type="apm_application">
    <license>GPL V2.0 or any later version</license>
    <package-name>Petri-Net Workflow</package-name>
    <pretty-plural>Petri-Net Workflow</pretty-plural>
@@ -9,18 +9,18 @@
    <singleton-p>t</singleton-p>
    <auto-mount>acs-workflow</auto-mount>

-    <version name="4.5.6" url="http://www.openacs.org/repository/download/apm/acs-workflow-4.5.6.apm">
+    <version name="4.5.6" url="https://www.openacs.org/repository/download/apm/acs-workflow-4.5.6.apm">
    <database-support>
        <database>oracle</database>
        <database>postgresql</database>
    </database-support>
-        <owner url="http://www.pinds.com/">Lars Pind</owner>
+        <owner url="https://www.pinds.com/">Lars Pind</owner>
        <owner url="mailto:k2pts@yahoo.com">Neophytos Demetriou</owner>
        <owner url="mailto:danw@rtp.ericsson.se">Daniel Wickstrom</owner>
        <owner url="mailto:frank.bergmann@project-open.com">Frank Bergmann</owner>
        <summary>Provides Petri-Net workflow management features to all ACS objects.</summary>
        <release-date>2002-05-15</release-date>
-        <vendor url="http://www.openacs.org/">OpenACS</vendor>
+        <vendor url="https://www.openacs.org/">OpenACS</vendor>

        <provides url="acs-workflow" version="4.5.6"/>
        <requires url="acs-kernel" version="4.6.2"/>

--- a/www/doc/advanced-workflow-builder.html
+++ b/www/doc/advanced-workflow-builder.html
@@ -10,7 +10,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Advanced Workflow Builder's Guide</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 30 August 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 30 August 2000.

 <p>


--- a/www/doc/concepts-reference.html
+++ b/www/doc/concepts-reference.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Concepts Reference</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 31 August 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 31 August 2000.

 <p>


--- a/www/doc/concepts.html
+++ b/www/doc/concepts.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Conceptual Guide</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 27 July 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 27 July 2000.

 <p>

@@ -57,7 +57,7 @@ href="order_wf.jpg" target=_new>open in separate window</a>)</small></td></tr>

 The definition of a workflows (what needs to be done to a case and in
 what order), are formalized in terms of a computational model called
-<a href="http://www.daimi.au.dk/PetriNets/" title="The main site for
+<a href="https://www.daimi.au.dk/PetriNets/" title="The main site for
 Colored Petri Nets (CPN) research"><b>Petri nets</b></a>, and the
 example above is indeed a Petri net. Let's walk through it and
 explain it in detail.
@@ -270,20 +270,20 @@ Developer's Guide</a> to learn how to use this with your own package.
 <ul>

 <li><a
-href="http://www.workflowsoftware.com/workflowwp.pdf"><em>Workflow
+href="https://www.workflowsoftware.com/workflowwp.pdf"><em>Workflow
 Technology - an Introduction</em></a>. A primer on automated workflow
 management.

 <p>

-<li><a href="http://www.wfmc.org/"><em>Workflow Management Coalition
+<li><a href="https://www.wfmc.org/"><em>Workflow Management Coalition
 (WfMC)</em></a>. They're the standards organization for the workflow
 industry. They devise standards for terminology and interoperability
 of workflow management software.

 <p>

-<li><a href="http://wwwis.win.tue.nl/~wsinwa/jcsc/jcsc.html"><em>The
+<li><a href="https://wwwis.win.tue.nl/~wsinwa/jcsc/jcsc.html"><em>The
 Application of Petri Nets to Workflow Management</em></a>. The
 arguments in this paper convinced us to use Petri nets as the
 foundation for our Workflow Engine.

--- a/www/doc/coordination.html
+++ b/www/doc/coordination.html
@@ -6,7 +6,7 @@
 <body bgcolor=white>
 <h2>Workflow Coordination Central</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on August 17, 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on August 17, 2000.

 <p>

@@ -26,7 +26,7 @@ Coordination Central
 <li>60. Email notifications from the engine. Stas has written a simple
 notification package: packages/notification (depends on
 packages/acs-util). Talk to <a
-href="http://www.arsdigita.com/shared/community-member?user_id=26556">Stas</a>
+href="https://www.arsdigita.com/shared/community-member?user_id=26556">Stas</a>
 about how to use it.

 <p>
@@ -58,7 +58,7 @@ there's currently no way to assign users to unassigned tasks.

 <li>360. Implement a function to check for soundness of the
 workflow-net: <a
-href="http://wwwis.win.tue.nl/~wsinwa/jcsc/node16.html#SECTION00052000000000000000">here's
+href="https://wwwis.win.tue.nl/~wsinwa/jcsc/node16.html#SECTION00052000000000000000">here's
 how</a>.

 </ul>

--- a/www/doc/design.html
+++ b/www/doc/design.html
@@ -11,7 +11,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Design Documentation</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 7 September 2000. <br><br>
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 7 September 2000. <br><br>
 By <a href="mailto:khy@arsdigita.com">Khy Huang</a> on 12 April 2001. 
 <p>

@@ -120,10 +120,10 @@ tools that will benefit users of any workflow-based application.
 <h3>IV.  Competitive Analysis</h3>

 The <strong>only open-source competitor</strong>, I've been able to locate is <a
-href="http://www.vivtek.com/wftk.html">wftk</a> by <a
-href="http://www.vivtek.com">Vivtek</a>. They have a fairly nice
+href="https://www.vivtek.com/wftk.html">wftk</a> by <a
+href="https://www.vivtek.com">Vivtek</a>. They have a fairly nice
 <a
-href="http://www.vivtek.com/workflow/wftk_exec/pdm/pdm.cgi">interface
+href="https://www.vivtek.com/workflow/wftk_exec/pdm/pdm.cgi">interface
 for defining workflow processes</a> that we could probably learn
 from. However, they've chosen a different model with explicit
 routing constructs, such as "sequential", "parallel", etc. It does
@@ -134,7 +134,7 @@ raising a "situation", and having a handler for that situation.

 We've also looked at, and strive to adhere to, the
 <strong>standards</strong> set forth by the <a
-href="http://www.wfmc.org">Workflow Management Coalition</a>.
+href="https://www.wfmc.org">Workflow Management Coalition</a>.

 <p>

@@ -172,7 +172,7 @@ Nets provides a formal mathematical model with an abundance of proven
 analysis techniques that can be used to both ensure static and dynamic
 properties of the workflow. Besides, W.M.P. van der Aalst made such a
 good argument in <a
-href="http://wwwis.win.tue.nl/~wsinwa/jcsc/jcsc.html"><em>The
+href="https://wwwis.win.tue.nl/~wsinwa/jcsc/jcsc.html"><em>The
 Application of Petri Nets to Workflow Management</em></a> that we felt
 confident it was the right decision. Parts of this argument is also
 that there are standard extensions to Petri Nets that are very useful
@@ -712,7 +712,7 @@ because these are necessary to understand how to build non-simple
 workflows. It would also allow the user to export the workflow in some
 way that is importable into another OpenACS installation for distribution
 either alone or with a package, either as a SQL file to load into the
-RDBMS, or as an XML in the <a href="http://www.wfmc.org">WfMC</a>
+RDBMS, or as an XML in the <a href="https://www.wfmc.org">WfMC</a>
 standard format.


@@ -732,7 +732,7 @@ verify what happened at each step of the execution.

 There are two optional parameters under the APM, 
 graphviz_dot_path and tmp_path.  These parameters are required for
-the <a href="http://www.research.att.com/sw/tools/graphviz/download.html">
+the <a href="https://www.research.att.com/sw/tools/graphviz/download.html">
 GraphVizv</a> program used to generated the diagrams.  Please read
 the installation guide for more details.


--- a/www/doc/developer.html
+++ b/www/doc/developer.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Developer's Guide</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 30 August 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 30 August 2000.

 <p>


--- a/www/doc/finishing.html
+++ b/www/doc/finishing.html
@@ -11,7 +11,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Finishing Proposal</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 22 September 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 22 September 2000.

 <p>


--- a/www/doc/future-plans.html
+++ b/www/doc/future-plans.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Future Plans</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 30 August 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 30 August 2000.

 <p>

@@ -62,7 +62,7 @@ on historic data.
 <li><strong>Cooperation with other systems.</strong> The workflow
 package should integrate with other software, including other workflow
 management systems. We're investigaing and evaluating the existing
-standards in the field, especially <a href="http://www.wfmc.org/">WfMC</a>.
+standards in the field, especially <a href="https://www.wfmc.org/">WfMC</a>.

 <p>


--- a/www/doc/index.html
+++ b/www/doc/index.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Package Overview</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 31 August 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 31 August 2000.

 <p>


--- a/www/doc/installation.html
+++ b/www/doc/installation.html
@@ -11,7 +11,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Installation and Getting Started Guide</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 26 October 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 26 October 2000.

 <p>

@@ -35,7 +35,7 @@ Workflow is installed by default on OpenACS 4.
 <ul>

 <li><a
-href="http://www.research.att.com/sw/tools/graphviz/download.html">GraphViz
+href="https://www.research.att.com/sw/tools/graphviz/download.html">GraphViz
 download page</a>

 </ul>
@@ -50,14 +50,14 @@ do install GraphViz.

 On RedHat 7.2, say:

-<pre>rpm -ivh http://www.research.att.com/sw/tools/graphviz/dist/graphviz-1.8.1-0.i386.rpm</pre>
+<pre>rpm -ivh https://www.research.att.com/sw/tools/graphviz/dist/graphviz-1.8.1-0.i386.rpm</pre>

 On Debian, say:

 <pre>apt-get install graphviz</pre>

 On other systems, visit the <a
-href="http://www.research.att.com/sw/tools/graphviz/download.html">GraphViz
+href="https://www.research.att.com/sw/tools/graphviz/download.html">GraphViz
 download page</a> and see what you can find out.

 </dd>
@@ -75,7 +75,7 @@ href="http://rpmfind.net/linux/RPM/contrib/noarch/noarch/webfonts-1-3.noarch.htm
 RPM</a> 

 or <a
-href="http://www.microsoft.com/typography/fontpack/default.htm">Microsoft
+href="https://www.microsoft.com/typography/fontpack/default.htm">Microsoft
 free TrueType font download page</a>

 </ul>
@@ -137,7 +137,7 @@ machine handy, you can download the <strong>Microsoft fonts</strong>:
 <ol>

 <li>Download and execute <a
-href="http://www.microsoft.com/typography/downloads/arial32.exe">arial32.exe</a>
+href="https://www.microsoft.com/typography/downloads/arial32.exe">arial32.exe</a>
 on a Windows machine.

 <li>Locate your font files in <code>c:\windows\fonts</code> or

--- a/www/doc/maintainer.html
+++ b/www/doc/maintainer.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Maintainer's Guide</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 27 July 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 27 July 2000.

 <p>


--- a/www/doc/overview.html
+++ b/www/doc/overview.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Conceptual Guide</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 27 July 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 27 July 2000.

 <p>


--- a/www/doc/petri-nets.html
+++ b/www/doc/petri-nets.html
@@ -6,7 +6,7 @@
 <body bgcolor=white>
 <h2>Petri Nets in the Workflow Package</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on 31 August 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on 31 August 2000.

 <hr>

@@ -134,12 +134,12 @@ extensively in simluation and verification of network protocols, a
 subject that is very like workflows in many ways. Therefore, it comes
 as no surprise that the concepts used in workflows maps onto Petri
 Nets in a very straight-forward way. If you're interested in reading
-more about this, <a href="http://wwwis.win.tue.nl/~wsinwa/">W.M.P. van
+more about this, <a href="https://wwwis.win.tue.nl/~wsinwa/">W.M.P. van
 der Aalst</a> has written an excellent paper, entitled <a
-href="http://wwwis.win.tue.nl/~wsinwa/jcsc/jcsc.html"><i>The
+href="https://wwwis.win.tue.nl/~wsinwa/jcsc/jcsc.html"><i>The
 Application of Petri Nets to Workflow Management</i></a>. Or, if
 you're lazy, you might want to <a
-href="http://wwwis.win.tue.nl/~wsinwa/jcsc/node24.html">just read the
+href="https://wwwis.win.tue.nl/~wsinwa/jcsc/node24.html">just read the
 conclusion</a> of the paper.

 <p>

--- a/www/doc/release-notes.html
+++ b/www/doc/release-notes.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Release Notes</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on December 19, 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on December 19, 2000.

 <p>


--- a/www/doc/requirements.html
+++ b/www/doc/requirements.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Requirements</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on November 8, 2000. <br>
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on November 8, 2000. <br>
 By <a href="mailto:khy@arsdigita.com">Khy Huang </a> on April 13, 2001
 <p>

@@ -155,10 +155,10 @@ application to different types of cases.
 <ul>

 <li><a
-href="http://www.aiim.org/wfmc/standards/docs/glossy3.pdf">Workflow
+href="https://www.aiim.org/wfmc/standards/docs/glossy3.pdf">Workflow
 Management Coalition's <i>Terminology and Glossary</i> document</a>
 (<a
-href="http://www.srdc.metu.edu.tr/metuflow/WfMC/WfMC_glossary.html">an
+href="https://www.srdc.metu.edu.tr/metuflow/WfMC/WfMC_glossary.html">an
 older version is available in HTML here</a>).

 </ul>

--- a/www/doc/support.html
+++ b/www/doc/support.html
@@ -9,7 +9,7 @@ dt { font-weight: bold; margin-top: 1em }
 <body bgcolor=white>
 <h2>Workflow Support Info</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on December 19, 2000.
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on December 19, 2000.

 <p>

@@ -22,20 +22,20 @@ Support Info

 <li><strong>If you need help</strong> beyond what the documentation
 has to offer, we have a <a
-href="http://www.arsdigita.com/bboard/q-and-a?topic_id=975">discussion
+href="https://www.arsdigita.com/bboard/q-and-a?topic_id=975">discussion
 forum</a> where you can ask questions to the developers of the
 workflow package, as well as the user community. Go to <a
-href="http://www.arsdigita.com/bboard/">http://arsdigita.com/bboard</a>
+href="https://www.arsdigita.com/bboard/">http://arsdigita.com/bboard</a>
 and click on the ACS Workflow Package Q&A Forum under Unmoderated
 Forums.

 <p>

 <li><strong>If you find bugs</strong>, visit the <a
-href="http://www.arsdigita.com/sdm/all-tickets?module_id=3613&package_id=3602&status=newopen">bug-tracker</a>
+href="https://www.arsdigita.com/sdm/all-tickets?module_id=3613&package_id=3602&status=newopen">bug-tracker</a>
 and check to see if it's already been reported, and otherwise report
 it. Go to <a
-href="http://www.arsdigita.com/sdm/">http://arsdigita.com/sdm</a> and
+href="https://www.arsdigita.com/sdm/">http://arsdigita.com/sdm</a> and
 navigate to the ArsDigita Community System (v4.x), then to the
 Workflow package, then finally click on Open Bugs and Features.


--- a/www/doc/workflow-scenarios.html
+++ b/www/doc/workflow-scenarios.html
@@ -6,7 +6,7 @@

 <h2>Workflow Scenarios</h2>

-By <a href="http://www.pinds.com/lars">Lars Pind</a> on June 7, 2000
+By <a href="https://www.pinds.com/lars">Lars Pind</a> on June 7, 2000

 <hr>