Not sure if it'll help - I couldn't understand <interpretonly>, but a combination of <noinclude></noinclude> and <includeonly></includeonly> usually works miracles ;)


On Feb 3, 2008 9:31 AM, Thomas Bäro <> wrote:
Hi there,

hm. Re-Reading my posting makes me warn you: This could be a little
confusing... I am sorry for the chaotic way of asking this question.

= A little explanation ahead of the real question =

I want to create a SMW that holds information about processes of
SW-Engineering such as Automotive SPICE (see ), CMMI, etc.

My approach is to copy the documents into the Wiki, creating pages for
each object that needs to be adressed explicitly. Since the data is
very structured I am using templates for the different types of
objects (Processes, Outcomes, Base Practices (BP), Work Products).

To display all the data of one process (for e.g.) I am also making use
of the template feature. An example is given below (see: A further

There you can see that I am including the page
{{:Standard:ASPICE/ACQ.4/BP1}} into the page
{{:Standard:ASPICE/ACQ.4}}. Later on the Page
{{:Standard:ASPICE/ACQ.4}} will also be included in

= The Question =

Is there an easy way to hide facts about a page when called through
the template function when the source page itself is using a template?

Or in other words: How can one go about when trying to make
"Template:ASPICE/BP" having only some properties that will be

= A non working solution to give further explanation =

This one doesn't work :-) But it would be great, if there would be a
solution to make this work. Let us assume we have Template:ASPICE/BP
looking like this:


<interpretonly>               <- doesnt exist !!!

     {{#if:{{{BPnote|}}} | [[BPnote:={{{BPnote}}}]]}}

= Explanation for <interpretonly> =

<interpretonly> tells the parser to interpret the following content
only when the template where <interpretonly> is used directly. This
way, one could have a <noinclude> in a template which will get
interpreted on the page that is using that template.

If you see Template:ASPICE/BP as a class definition it would then have
annotations that are publicly available when used (ie BPtitle) and
other annotations that are only available on the page directly (ie

= A further Example =

== The process template in use ==

|ProcessName=Supplier monitoring
|ProcessPurpose=The purpose of the Supplier monitoring process is to
monitor the performance of the supplier against agreed requirements.
|Outcomes={{:Standard:ASPICE/ACQ.4/Outcome 1}}
|WP1o=[[Standard:ASPICE/ACQ.4/Outcome 5|5]]

== The base practice template in use ==

|BPtitle=Negotiate the contract / agreement.
|BPtext=Negotiate all relevant aspects of the contract / agreement
with the supplier.
|BPoutcome=[[Standard:ASPICE/ACQ.3/Outcome 1|1]]
|BPnote=NOTE 1: Relevant aspects of the procurement may include
* system requirements
* acceptance criteria and evaluation criteria
* linkage between payment and successful completion of acceptance testing
* process requirements, process interfaces and joint processes.


This email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Semediawiki-user mailing list

Sergey Chernyshev