glossary enrichment proposal

[Rajesh Mallah]

Hi ,

We use many technical terms throughout the pages and articles but
the interpretation of the term may be  open or approximate to various
stakeholders due to lack of common definitions and glossary.


We already have a glossary page
https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
But it is not very exhaustive yet.

I was planning to go through the BPRB pages and prepare a list of all
technical terms used in various pages for the purpose of enriching
(extending) the glossary.

I invite opinions on whether it is worth ?

My Arguments in favour:

(1) We need a common plane for definitions, if there is a disparity between
      author's interpretation of a business term and the reader's or
      reviewer's interpretation there shall be a communication gap.

(2) For newbies it is a great resource  because it increases their
      knowledge as well as ability of understanding more articles/pages.

(3) consistency of articles: if all authors/contributors use the same
terminology
      then the content created by them shall relate to each other in a more
      consistent manner.

Implementation notes:
----------------------------
currently we have our glossary in a flat list format with is the easiest way
to get started. However as the volume of terms and documentation increases
we shall also require to organise the glossary in a more methodical way.
Some of the relevant standards are W3C standards like SKOS [1]  , OWL[2].
I am not sure if confluence has components that allow organising vocabulary
at this moment.

Even if its' not there we can continue to enrich the Glossary / Vocab in a
simple
manner (and later migrate/upgrade it).


References:
[1] https://www.w3.org/2004/02/skos/intro
[2] https://www.w3.org/2001/sw/wiki/OWL

[Jacques Le Roux]

+1

Jacques


Le 29/08/2017 à 12:07, Rajesh Mallah a écrit :

> Hi ,
>
> We use many technical terms throughout the pages and articles but
> the interpretation of the term may be  open or approximate to various
> stakeholders due to lack of common definitions and glossary.
>
>
> We already have a glossary page
> https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> But it is not very exhaustive yet.
>
> I was planning to go through the BPRB pages and prepare a list of all
> technical terms used in various pages for the purpose of enriching
> (extending) the glossary.
>
> I invite opinions on whether it is worth ?
>
> My Arguments in favour:
>
> (1) We need a common plane for definitions, if there is a disparity between
>        author's interpretation of a business term and the reader's or
>        reviewer's interpretation there shall be a communication gap.
>
> (2) For newbies it is a great resource  because it increases their
>        knowledge as well as ability of understanding more articles/pages.
>
> (3) consistency of articles: if all authors/contributors use the same
> terminology
>        then the content created by them shall relate to each other in a more
>        consistent manner.
>
> Implementation notes:
> ----------------------------
> currently we have our glossary in a flat list format with is the easiest way
> to get started. However as the volume of terms and documentation increases
> we shall also require to organise the glossary in a more methodical way.
> Some of the relevant standards are W3C standards like SKOS [1]  , OWL[2].
> I am not sure if confluence has components that allow organising vocabulary
> at this moment.
>
> Even if its' not there we can continue to enrich the Glossary / Vocab in a
> simple
> manner (and later migrate/upgrade it).
>
>
> References:
> [1] https://www.w3.org/2004/02/skos/intro
> [2] https://www.w3.org/2001/sw/wiki/OWL
>

[Devanshu Vyas-2]

I like the idea, +1.

Thanks & Regards,
Devanshu Vyas.

On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <[hidden email]>
wrote:

> Hi ,
>
> We use many technical terms throughout the pages and articles but
> the interpretation of the term may be  open or approximate to various
> stakeholders due to lack of common definitions and glossary.
>
>
> We already have a glossary page
> https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> But it is not very exhaustive yet.
>
> I was planning to go through the BPRB pages and prepare a list of all
> technical terms used in various pages for the purpose of enriching
> (extending) the glossary.
>
> I invite opinions on whether it is worth ?
>
> My Arguments in favour:
>
> (1) We need a common plane for definitions, if there is a disparity between
>       author's interpretation of a business term and the reader's or
>       reviewer's interpretation there shall be a communication gap.
>
> (2) For newbies it is a great resource  because it increases their
>       knowledge as well as ability of understanding more articles/pages.
>
> (3) consistency of articles: if all authors/contributors use the same
> terminology
>       then the content created by them shall relate to each other in a more
>       consistent manner.
>
> Implementation notes:
> ----------------------------
> currently we have our glossary in a flat list format with is the easiest
> way
> to get started. However as the volume of terms and documentation increases
> we shall also require to organise the glossary in a more methodical way.
> Some of the relevant standards are W3C standards like SKOS [1]  , OWL[2].
> I am not sure if confluence has components that allow organising vocabulary
> at this moment.
>
> Even if its' not there we can continue to enrich the Glossary / Vocab in a
> simple
> manner (and later migrate/upgrade it).
>
>
> References:
> [1] https://www.w3.org/2004/02/skos/intro
> [2] https://www.w3.org/2001/sw/wiki/OWL
>

[Sonal Patwari]

Nice idea, thanks Rajesh!

Regards,

Sonal Patwari
Enterprise Software Engineer
HotWax Systems <http://www.hotwaxsystems.com/>


On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <[hidden email]>
wrote:

> I like the idea, +1.
>
> Thanks & Regards,
> Devanshu Vyas.
>
> On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <[hidden email]>
> wrote:
>
> > Hi ,
> >
> > We use many technical terms throughout the pages and articles but
> > the interpretation of the term may be  open or approximate to various
> > stakeholders due to lack of common definitions and glossary.
> >
> >
> > We already have a glossary page
> > https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> > But it is not very exhaustive yet.
> >
> > I was planning to go through the BPRB pages and prepare a list of all
> > technical terms used in various pages for the purpose of enriching
> > (extending) the glossary.
> >
> > I invite opinions on whether it is worth ?
> >
> > My Arguments in favour:
> >
> > (1) We need a common plane for definitions, if there is a disparity
> between
> >       author's interpretation of a business term and the reader's or
> >       reviewer's interpretation there shall be a communication gap.
> >
> > (2) For newbies it is a great resource  because it increases their
> >       knowledge as well as ability of understanding more articles/pages.
> >
> > (3) consistency of articles: if all authors/contributors use the same
> > terminology
> >       then the content created by them shall relate to each other in a
> more
> >       consistent manner.
> >
> > Implementation notes:
> > ----------------------------
> > currently we have our glossary in a flat list format with is the easiest
> > way
> > to get started. However as the volume of terms and documentation
> increases
> > we shall also require to organise the glossary in a more methodical way.
> > Some of the relevant standards are W3C standards like SKOS [1]  , OWL[2].
> > I am not sure if confluence has components that allow organising
> vocabulary
> > at this moment.
> >
> > Even if its' not there we can continue to enrich the Glossary / Vocab in
> a
> > simple
> > manner (and later migrate/upgrade it).
> >
> >
> > References:
> > [1] https://www.w3.org/2004/02/skos/intro
> > [2] https://www.w3.org/2001/sw/wiki/OWL
> >
>

[Shivangi Tanwar]

+1 for the idea.

Few More Suggestions:

1) Glossary of terms can also be bifurcated based on business processes or
OFBiz components. For Example, inventory can have business terms like ATP,
QOH, Back Order etc.
2) We can also incorporate business terminologies used in real world. So,
people can relate those terms to the framework.

Also, I would like to contribute to this glossary enrichment effort too.

Thanks and Regards,

Shivangi Tanwar

On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <[hidden email]>
wrote:

> I like the idea, +1.
>
> Thanks & Regards,
> Devanshu Vyas.
>
> On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <[hidden email]>
> wrote:
>
> > Hi ,
> >
> > We use many technical terms throughout the pages and articles but
> > the interpretation of the term may be  open or approximate to various
> > stakeholders due to lack of common definitions and glossary.
> >
> >
> > We already have a glossary page
> > https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> > But it is not very exhaustive yet.
> >
> > I was planning to go through the BPRB pages and prepare a list of all
> > technical terms used in various pages for the purpose of enriching
> > (extending) the glossary.
> >
> > I invite opinions on whether it is worth ?
> >
> > My Arguments in favour:
> >
> > (1) We need a common plane for definitions, if there is a disparity
> between
> >       author's interpretation of a business term and the reader's or
> >       reviewer's interpretation there shall be a communication gap.
> >
> > (2) For newbies it is a great resource  because it increases their
> >       knowledge as well as ability of understanding more articles/pages.
> >
> > (3) consistency of articles: if all authors/contributors use the same
> > terminology
> >       then the content created by them shall relate to each other in a
> more
> >       consistent manner.
> >
> > Implementation notes:
> > ----------------------------
> > currently we have our glossary in a flat list format with is the easiest
> > way
> > to get started. However as the volume of terms and documentation
> increases
> > we shall also require to organise the glossary in a more methodical way.
> > Some of the relevant standards are W3C standards like SKOS [1]  , OWL[2].
> > I am not sure if confluence has components that allow organising
> vocabulary
> > at this moment.
> >
> > Even if its' not there we can continue to enrich the Glossary / Vocab in
> a
> > simple
> > manner (and later migrate/upgrade it).
> >
> >
> > References:
> > [1] https://www.w3.org/2004/02/skos/intro
> > [2] https://www.w3.org/2001/sw/wiki/OWL
> >
>

[Sanjay Yadav]

Nice idea Rajesh, Shivangi.

+1

Best Regards,

*Sanjay Yadav *
Manager, Enterprise Quality Assurance
www.hotwaxsystems.com
www.hotwax.co

On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
[hidden email]> wrote:

> +1 for the idea.
>
> Few More Suggestions:
>
> 1) Glossary of terms can also be bifurcated based on business processes or
> OFBiz components. For Example, inventory can have business terms like ATP,
> QOH, Back Order etc.
> 2) We can also incorporate business terminologies used in real world. So,
> people can relate those terms to the framework.
>
> Also, I would like to contribute to this glossary enrichment effort too.
>
> Thanks and Regards,
>
> Shivangi Tanwar
>
> On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <[hidden email]>
> wrote:
>
> > I like the idea, +1.
> >
> > Thanks & Regards,
> > Devanshu Vyas.
> >
> > On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <[hidden email]>
> > wrote:
> >
> > > Hi ,
> > >
> > > We use many technical terms throughout the pages and articles but
> > > the interpretation of the term may be  open or approximate to various
> > > stakeholders due to lack of common definitions and glossary.
> > >
> > >
> > > We already have a glossary page
> > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> > > But it is not very exhaustive yet.
> > >
> > > I was planning to go through the BPRB pages and prepare a list of all
> > > technical terms used in various pages for the purpose of enriching
> > > (extending) the glossary.
> > >
> > > I invite opinions on whether it is worth ?
> > >
> > > My Arguments in favour:
> > >
> > > (1) We need a common plane for definitions, if there is a disparity
> > between
> > >       author's interpretation of a business term and the reader's or
> > >       reviewer's interpretation there shall be a communication gap.
> > >
> > > (2) For newbies it is a great resource  because it increases their
> > >       knowledge as well as ability of understanding more
> articles/pages.
> > >
> > > (3) consistency of articles: if all authors/contributors use the same
> > > terminology
> > >       then the content created by them shall relate to each other in a
> > more
> > >       consistent manner.
> > >
> > > Implementation notes:
> > > ----------------------------
> > > currently we have our glossary in a flat list format with is the
> easiest
> > > way
> > > to get started. However as the volume of terms and documentation
> > increases
> > > we shall also require to organise the glossary in a more methodical
> way.
> > > Some of the relevant standards are W3C standards like SKOS [1]  ,
> OWL[2].
> > > I am not sure if confluence has components that allow organising
> > vocabulary
> > > at this moment.
> > >
> > > Even if its' not there we can continue to enrich the Glossary / Vocab
> in
> > a
> > > simple
> > > manner (and later migrate/upgrade it).
> > >
> > >
> > > References:
> > > [1] https://www.w3.org/2004/02/skos/intro
> > > [2] https://www.w3.org/2001/sw/wiki/OWL
> > >
> >
>

[Rajesh Mallah]

Thanks for the kind words everyone.

I already created a scratchpad

https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73635445

it is my first page and i feel it got created in a wrong place.  :D

request senior members to kindly relocate to a more suitable place.

regds
mallah.





On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
[hidden email]> wrote:

> +1 for the idea.
>
> Few More Suggestions:
>
> 1) Glossary of terms can also be bifurcated based on business processes or
> OFBiz components. For Example, inventory can have business terms like ATP,
> QOH, Back Order etc.
> 2) We can also incorporate business terminologies used in real world. So,
> people can relate those terms to the framework.
>
> Also, I would like to contribute to this glossary enrichment effort too.
>
> Thanks and Regards,
>
> Shivangi Tanwar
>
> On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <[hidden email]>
> wrote:
>
> > I like the idea, +1.
> >
> > Thanks & Regards,
> > Devanshu Vyas.
> >
> > On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <[hidden email]>
> > wrote:
> >
> > > Hi ,
> > >
> > > We use many technical terms throughout the pages and articles but
> > > the interpretation of the term may be  open or approximate to various
> > > stakeholders due to lack of common definitions and glossary.
> > >
> > >
> > > We already have a glossary page
> > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> > > But it is not very exhaustive yet.
> > >
> > > I was planning to go through the BPRB pages and prepare a list of all
> > > technical terms used in various pages for the purpose of enriching
> > > (extending) the glossary.
> > >
> > > I invite opinions on whether it is worth ?
> > >
> > > My Arguments in favour:
> > >
> > > (1) We need a common plane for definitions, if there is a disparity
> > between
> > >       author's interpretation of a business term and the reader's or
> > >       reviewer's interpretation there shall be a communication gap.
> > >
> > > (2) For newbies it is a great resource  because it increases their
> > >       knowledge as well as ability of understanding more
> articles/pages.
> > >
> > > (3) consistency of articles: if all authors/contributors use the same
> > > terminology
> > >       then the content created by them shall relate to each other in a
> > more
> > >       consistent manner.
> > >
> > > Implementation notes:
> > > ----------------------------
> > > currently we have our glossary in a flat list format with is the
> easiest
> > > way
> > > to get started. However as the volume of terms and documentation
> > increases
> > > we shall also require to organise the glossary in a more methodical
> way.
> > > Some of the relevant standards are W3C standards like SKOS [1]  ,
> OWL[2].
> > > I am not sure if confluence has components that allow organising
> > vocabulary
> > > at this moment.
> > >
> > > Even if its' not there we can continue to enrich the Glossary / Vocab
> in
> > a
> > > simple
> > > manner (and later migrate/upgrade it).
> > >
> > >
> > > References:
> > > [1] https://www.w3.org/2004/02/skos/intro
> > > [2] https://www.w3.org/2001/sw/wiki/OWL
> > >
> >
>

[Rajesh Mallah]

Hi Shivangi ,

pls find replies inline.

On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
[hidden email]> wrote:

> +1 for the idea.
>
> Few More Suggestions:
>
> 1) Glossary of terms can also be bifurcated based on business processes or
> OFBiz components. For Example, inventory can have business terms like ATP,
> QOH, Back Order etc.
> 2) We can also incorporate business terminologies used in real world. So,
> people can relate those terms to the framework.
>
>

Both the above requirements are covered in a generic manner via various
relationship
mechanism in  SKOS system , I am hopeful confluence would have some plugin
that
allows to leverage on that or some related technology or standard for
maintaining vocabs
and semantic relations between terms  . ( I  would explore at some point )

SKOS article ( 2-3 mins reading time ).
 https://en.wikipedia.org/wiki/Simple_Knowledge_Organization_System#Concepts

I also observe that certain SKOS concept are already in use in Catalog >
Thesaurus application.

Also, I would like to contribute to this glossary enrichment effort too.
>

Sure ! & thanks  , its being done as a Wiki page only. As a matter of fact
contribution and enrichment to definitions should done by banking upon
existing definitions and on knowledge which can be borrowed on reliable
sources . (no point re-inventing , definitions , we have to put it in
context
of ofbiz only ).


regds
mallah.

>
> Thanks and Regards,
>
> Shivangi Tanwar
>
> On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <[hidden email]>
> wrote:
>
> > I like the idea, +1.
> >
> > Thanks & Regards,
> > Devanshu Vyas.
> >
> > On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <[hidden email]>
> > wrote:
> >
> > > Hi ,
> > >
> > > We use many technical terms throughout the pages and articles but
> > > the interpretation of the term may be  open or approximate to various
> > > stakeholders due to lack of common definitions and glossary.
> > >
> > >
> > > We already have a glossary page
> > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> > > But it is not very exhaustive yet.
> > >
> > > I was planning to go through the BPRB pages and prepare a list of all
> > > technical terms used in various pages for the purpose of enriching
> > > (extending) the glossary.
> > >
> > > I invite opinions on whether it is worth ?
> > >
> > > My Arguments in favour:
> > >
> > > (1) We need a common plane for definitions, if there is a disparity
> > between
> > >       author's interpretation of a business term and the reader's or
> > >       reviewer's interpretation there shall be a communication gap.
> > >
> > > (2) For newbies it is a great resource  because it increases their
> > >       knowledge as well as ability of understanding more
> articles/pages.
> > >
> > > (3) consistency of articles: if all authors/contributors use the same
> > > terminology
> > >       then the content created by them shall relate to each other in a
> > more
> > >       consistent manner.
> > >
> > > Implementation notes:
> > > ----------------------------
> > > currently we have our glossary in a flat list format with is the
> easiest
> > > way
> > > to get started. However as the volume of terms and documentation
> > increases
> > > we shall also require to organise the glossary in a more methodical
> way.
> > > Some of the relevant standards are W3C standards like SKOS [1]  ,
> OWL[2].
> > > I am not sure if confluence has components that allow organising
> > vocabulary
> > > at this moment.
> > >
> > > Even if its' not there we can continue to enrich the Glossary / Vocab
> in
> > a
> > > simple
> > > manner (and later migrate/upgrade it).
> > >
> > >
> > > References:
> > > [1] https://www.w3.org/2004/02/skos/intro
> > > [2] https://www.w3.org/2001/sw/wiki/OWL
> > >
> >
>

[Ankit Joshi]

+1 for the Idea.

Thanks & Regards,
Ankit Joshi


On Tue, Aug 29, 2017 at 5:13 PM, Rajesh Mallah <[hidden email]>
wrote:

> Hi Shivangi ,
>
> pls find replies inline.
>
> On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
> [hidden email]> wrote:
>
> > +1 for the idea.
> >
> > Few More Suggestions:
> >
> > 1) Glossary of terms can also be bifurcated based on business processes
> or
> > OFBiz components. For Example, inventory can have business terms like
> ATP,
> > QOH, Back Order etc.
> > 2) We can also incorporate business terminologies used in real world. So,
> > people can relate those terms to the framework.
> >
> >
> Both the above requirements are covered in a generic manner via various
> relationship
> mechanism in  SKOS system , I am hopeful confluence would have some plugin
> that
> allows to leverage on that or some related technology or standard for
> maintaining vocabs
> and semantic relations between terms  . ( I  would explore at some point )
>
> SKOS article ( 2-3 mins reading time ).
>  https://en.wikipedia.org/wiki/Simple_Knowledge_
> Organization_System#Concepts
>
> I also observe that certain SKOS concept are already in use in Catalog >
> Thesaurus application.
>
> Also, I would like to contribute to this glossary enrichment effort too.
> >
>
> Sure ! & thanks  , its being done as a Wiki page only. As a matter of fact
> contribution and enrichment to definitions should done by banking upon
> existing definitions and on knowledge which can be borrowed on reliable
> sources . (no point re-inventing , definitions , we have to put it in
> context
> of ofbiz only ).
>
>
> regds
> mallah.
>
>
> >
> > Thanks and Regards,
> >
> > Shivangi Tanwar
> >
> > On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <
> [hidden email]>
> > wrote:
> >
> > > I like the idea, +1.
> > >
> > > Thanks & Regards,
> > > Devanshu Vyas.
> > >
> > > On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <
> [hidden email]>
> > > wrote:
> > >
> > > > Hi ,
> > > >
> > > > We use many technical terms throughout the pages and articles but
> > > > the interpretation of the term may be  open or approximate to various
> > > > stakeholders due to lack of common definitions and glossary.
> > > >
> > > >
> > > > We already have a glossary page
> > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> > > > But it is not very exhaustive yet.
> > > >
> > > > I was planning to go through the BPRB pages and prepare a list of all
> > > > technical terms used in various pages for the purpose of enriching
> > > > (extending) the glossary.
> > > >
> > > > I invite opinions on whether it is worth ?
> > > >
> > > > My Arguments in favour:
> > > >
> > > > (1) We need a common plane for definitions, if there is a disparity
> > > between
> > > >       author's interpretation of a business term and the reader's or
> > > >       reviewer's interpretation there shall be a communication gap.
> > > >
> > > > (2) For newbies it is a great resource  because it increases their
> > > >       knowledge as well as ability of understanding more
> > articles/pages.
> > > >
> > > > (3) consistency of articles: if all authors/contributors use the same
> > > > terminology
> > > >       then the content created by them shall relate to each other in
> a
> > > more
> > > >       consistent manner.
> > > >
> > > > Implementation notes:
> > > > ----------------------------
> > > > currently we have our glossary in a flat list format with is the
> > easiest
> > > > way
> > > > to get started. However as the volume of terms and documentation
> > > increases
> > > > we shall also require to organise the glossary in a more methodical
> > way.
> > > > Some of the relevant standards are W3C standards like SKOS [1]  ,
> > OWL[2].
> > > > I am not sure if confluence has components that allow organising
> > > vocabulary
> > > > at this moment.
> > > >
> > > > Even if its' not there we can continue to enrich the Glossary / Vocab
> > in
> > > a
> > > > simple
> > > > manner (and later migrate/upgrade it).
> > > >
> > > >
> > > > References:
> > > > [1] https://www.w3.org/2004/02/skos/intro
> > > > [2] https://www.w3.org/2001/sw/wiki/OWL
> > > >
> > >
> >
>

[Rajesh Mallah]

can someone conversant with confluence/wiki point me to list of *all* pages
created under

https://cwiki.apache.org/confluence/display/OFBIZ/Business+Process+Reference+Book

else i have to create the list in the hard way (manually).

regds
mallah.


On Tue, Aug 29, 2017 at 5:27 PM, Ankit Joshi <[hidden email]>
wrote:

> +1 for the Idea.
>
> Thanks & Regards,
> Ankit Joshi
>
>
> On Tue, Aug 29, 2017 at 5:13 PM, Rajesh Mallah <[hidden email]>
> wrote:
>
> > Hi Shivangi ,
> >
> > pls find replies inline.
> >
> > On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
> > [hidden email]> wrote:
> >
> > > +1 for the idea.
> > >
> > > Few More Suggestions:
> > >
> > > 1) Glossary of terms can also be bifurcated based on business processes
> > or
> > > OFBiz components. For Example, inventory can have business terms like
> > ATP,
> > > QOH, Back Order etc.
> > > 2) We can also incorporate business terminologies used in real world.
> So,
> > > people can relate those terms to the framework.
> > >
> > >
> > Both the above requirements are covered in a generic manner via various
> > relationship
> > mechanism in  SKOS system , I am hopeful confluence would have some
> plugin
> > that
> > allows to leverage on that or some related technology or standard for
> > maintaining vocabs
> > and semantic relations between terms  . ( I  would explore at some point
> )
> >
> > SKOS article ( 2-3 mins reading time ).
> >  https://en.wikipedia.org/wiki/Simple_Knowledge_
> > Organization_System#Concepts
> >
> > I also observe that certain SKOS concept are already in use in Catalog >
> > Thesaurus application.
> >
> > Also, I would like to contribute to this glossary enrichment effort too.
> > >
> >
> > Sure ! & thanks  , its being done as a Wiki page only. As a matter of
> fact
> > contribution and enrichment to definitions should done by banking upon
> > existing definitions and on knowledge which can be borrowed on reliable
> > sources . (no point re-inventing , definitions , we have to put it in
> > context
> > of ofbiz only ).
> >
> >
> > regds
> > mallah.
> >
> >
> > >
> > > Thanks and Regards,
> > >
> > > Shivangi Tanwar
> > >
> > > On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <
> > [hidden email]>
> > > wrote:
> > >
> > > > I like the idea, +1.
> > > >
> > > > Thanks & Regards,
> > > > Devanshu Vyas.
> > > >
> > > > On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <
> > [hidden email]>
> > > > wrote:
> > > >
> > > > > Hi ,
> > > > >
> > > > > We use many technical terms throughout the pages and articles but
> > > > > the interpretation of the term may be  open or approximate to
> various
> > > > > stakeholders due to lack of common definitions and glossary.
> > > > >
> > > > >
> > > > > We already have a glossary page
> > > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> > > > > But it is not very exhaustive yet.
> > > > >
> > > > > I was planning to go through the BPRB pages and prepare a list of
> all
> > > > > technical terms used in various pages for the purpose of enriching
> > > > > (extending) the glossary.
> > > > >
> > > > > I invite opinions on whether it is worth ?
> > > > >
> > > > > My Arguments in favour:
> > > > >
> > > > > (1) We need a common plane for definitions, if there is a disparity
> > > > between
> > > > >       author's interpretation of a business term and the reader's
> or
> > > > >       reviewer's interpretation there shall be a communication gap.
> > > > >
> > > > > (2) For newbies it is a great resource  because it increases their
> > > > >       knowledge as well as ability of understanding more
> > > articles/pages.
> > > > >
> > > > > (3) consistency of articles: if all authors/contributors use the
> same
> > > > > terminology
> > > > >       then the content created by them shall relate to each other
> in
> > a
> > > > more
> > > > >       consistent manner.
> > > > >
> > > > > Implementation notes:
> > > > > ----------------------------
> > > > > currently we have our glossary in a flat list format with is the
> > > easiest
> > > > > way
> > > > > to get started. However as the volume of terms and documentation
> > > > increases
> > > > > we shall also require to organise the glossary in a more methodical
> > > way.
> > > > > Some of the relevant standards are W3C standards like SKOS [1]  ,
> > > OWL[2].
> > > > > I am not sure if confluence has components that allow organising
> > > > vocabulary
> > > > > at this moment.
> > > > >
> > > > > Even if its' not there we can continue to enrich the Glossary /
> Vocab
> > > in
> > > > a
> > > > > simple
> > > > > manner (and later migrate/upgrade it).
> > > > >
> > > > >
> > > > > References:
> > > > > [1] https://www.w3.org/2004/02/skos/intro
> > > > > [2] https://www.w3.org/2001/sw/wiki/OWL
> > > > >
> > > >
> > >
> >
>

[Rishi Solanki]

+1 for the idea Rajesh.

To answer your question, did you notice the child pages in the bottom?

Here is quick reference;
Page: Customer Relationship Management (CRM)
<https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73634368>
Page: E-commerce
<https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce>
Page: Financial Accounting and Reporting
<https://cwiki.apache.org/confluence/display/OFBIZ/Financial+Accounting+and+Reporting>
Page: Human Resources Management
<https://cwiki.apache.org/confluence/display/OFBIZ/Human+Resources+Management>
Page: Manufacturing
<https://cwiki.apache.org/confluence/display/OFBIZ/Manufacturing>
Page: Order Fulfillment Process
<https://cwiki.apache.org/confluence/display/OFBIZ/Order+Fulfillment+Process>
Page: Party <https://cwiki.apache.org/confluence/display/OFBIZ/Party>
Page: Product Information Management (PIM)
<https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=46631782>
Page: Sales Order Management
<https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management>
Page: Supply Chain Planning
<https://cwiki.apache.org/confluence/display/OFBIZ/Supply+Chain+Planning>
Page: Warehouse Management
<https://cwiki.apache.org/confluence/display/OFBIZ/Warehouse+Management>


Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: [phone]
http://www.hotwaxsystems.com
www.hotwax.co

On Tue, Aug 29, 2017 at 5:32 PM, Rajesh Mallah <[hidden email]>
wrote:

> can someone conversant with confluence/wiki point me to list of *all* pages
> created under
>
> https://cwiki.apache.org/confluence/display/OFBIZ/
> Business+Process+Reference+Book
>
> else i have to create the list in the hard way (manually).
>
> regds
> mallah.
>
>
> On Tue, Aug 29, 2017 at 5:27 PM, Ankit Joshi <
> [hidden email]>
> wrote:
>
> > +1 for the Idea.
> >
> > Thanks & Regards,
> > Ankit Joshi
> >
> >
> > On Tue, Aug 29, 2017 at 5:13 PM, Rajesh Mallah <[hidden email]>
> > wrote:
> >
> > > Hi Shivangi ,
> > >
> > > pls find replies inline.
> > >
> > > On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
> > > [hidden email]> wrote:
> > >
> > > > +1 for the idea.
> > > >
> > > > Few More Suggestions:
> > > >
> > > > 1) Glossary of terms can also be bifurcated based on business
> processes
> > > or
> > > > OFBiz components. For Example, inventory can have business terms like
> > > ATP,
> > > > QOH, Back Order etc.
> > > > 2) We can also incorporate business terminologies used in real world.
> > So,
> > > > people can relate those terms to the framework.
> > > >
> > > >
> > > Both the above requirements are covered in a generic manner via various
> > > relationship
> > > mechanism in  SKOS system , I am hopeful confluence would have some
> > plugin
> > > that
> > > allows to leverage on that or some related technology or standard for
> > > maintaining vocabs
> > > and semantic relations between terms  . ( I  would explore at some
> point
> > )
> > >
> > > SKOS article ( 2-3 mins reading time ).
> > >  https://en.wikipedia.org/wiki/Simple_Knowledge_
> > > Organization_System#Concepts
> > >
> > > I also observe that certain SKOS concept are already in use in Catalog
> >
> > > Thesaurus application.
> > >
> > > Also, I would like to contribute to this glossary enrichment effort
> too.
> > > >
> > >
> > > Sure ! & thanks  , its being done as a Wiki page only. As a matter of
> > fact
> > > contribution and enrichment to definitions should done by banking upon
> > > existing definitions and on knowledge which can be borrowed on reliable
> > > sources . (no point re-inventing , definitions , we have to put it in
> > > context
> > > of ofbiz only ).
> > >
> > >
> > > regds
> > > mallah.
> > >
> > >
> > > >
> > > > Thanks and Regards,
> > > >
> > > > Shivangi Tanwar
> > > >
> > > > On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <
> > > [hidden email]>
> > > > wrote:
> > > >
> > > > > I like the idea, +1.
> > > > >
> > > > > Thanks & Regards,
> > > > > Devanshu Vyas.
> > > > >
> > > > > On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <
> > > [hidden email]>
> > > > > wrote:
> > > > >
> > > > > > Hi ,
> > > > > >
> > > > > > We use many technical terms throughout the pages and articles but
> > > > > > the interpretation of the term may be  open or approximate to
> > various
> > > > > > stakeholders due to lack of common definitions and glossary.
> > > > > >
> > > > > >
> > > > > > We already have a glossary page
> > > > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> > > > > > But it is not very exhaustive yet.
> > > > > >
> > > > > > I was planning to go through the BPRB pages and prepare a list of
> > all
> > > > > > technical terms used in various pages for the purpose of
> enriching
> > > > > > (extending) the glossary.
> > > > > >
> > > > > > I invite opinions on whether it is worth ?
> > > > > >
> > > > > > My Arguments in favour:
> > > > > >
> > > > > > (1) We need a common plane for definitions, if there is a
> disparity
> > > > > between
> > > > > >       author's interpretation of a business term and the reader's
> > or
> > > > > >       reviewer's interpretation there shall be a communication
> gap.
> > > > > >
> > > > > > (2) For newbies it is a great resource  because it increases
> their
> > > > > >       knowledge as well as ability of understanding more
> > > > articles/pages.
> > > > > >
> > > > > > (3) consistency of articles: if all authors/contributors use the
> > same
> > > > > > terminology
> > > > > >       then the content created by them shall relate to each other
> > in
> > > a
> > > > > more
> > > > > >       consistent manner.
> > > > > >
> > > > > > Implementation notes:
> > > > > > ----------------------------
> > > > > > currently we have our glossary in a flat list format with is the
> > > > easiest
> > > > > > way
> > > > > > to get started. However as the volume of terms and documentation
> > > > > increases
> > > > > > we shall also require to organise the glossary in a more
> methodical
> > > > way.
> > > > > > Some of the relevant standards are W3C standards like SKOS [1]  ,
> > > > OWL[2].
> > > > > > I am not sure if confluence has components that allow organising
> > > > > vocabulary
> > > > > > at this moment.
> > > > > >
> > > > > > Even if its' not there we can continue to enrich the Glossary /
> > Vocab
> > > > in
> > > > > a
> > > > > > simple
> > > > > > manner (and later migrate/upgrade it).
> > > > > >
> > > > > >
> > > > > > References:
> > > > > > [1] https://www.w3.org/2004/02/skos/intro
> > > > > > [2] https://www.w3.org/2001/sw/wiki/OWL
> > > > > >
> > > > >
> > > >
> > >
> >
>

[Jacques Le Roux]

Rajesh,

Something you want to avoid in Confluence titles are special characters.

Confluence does not handle them well and so create URLs for the page like yours below.

I replaced & by and and the page is now at https://cwiki.apache.org/confluence/display/OFBIZ/ScratchPad+for+collecting+Terms+and+Acronyms

It's under Home wich is fine for now because it's only a temporary page. Later we would want to move it directly under
https://cwiki.apache.org/confluence/display/OFBIZ/Documentation

HTH

Jacques


Le 29/08/2017 à 13:23, Rajesh Mallah a écrit :

> Thanks for the kind words everyone.
>
> I already created a scratchpad
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73635445
>
> it is my first page and i feel it got created in a wrong place.  :D
>
> request senior members to kindly relocate to a more suitable place.
>
> regds
> mallah.
>
>
>
>
>
> On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
> [hidden email]> wrote:
>
>> +1 for the idea.
>>
>> Few More Suggestions:
>>
>> 1) Glossary of terms can also be bifurcated based on business processes or
>> OFBiz components. For Example, inventory can have business terms like ATP,
>> QOH, Back Order etc.
>> 2) We can also incorporate business terminologies used in real world. So,
>> people can relate those terms to the framework.
>>
>> Also, I would like to contribute to this glossary enrichment effort too.
>>
>> Thanks and Regards,
>>
>> Shivangi Tanwar
>>
>> On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <[hidden email]>
>> wrote:
>>
>>> I like the idea, +1.
>>>
>>> Thanks & Regards,
>>> Devanshu Vyas.
>>>
>>> On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <[hidden email]>
>>> wrote:
>>>
>>>> Hi ,
>>>>
>>>> We use many technical terms throughout the pages and articles but
>>>> the interpretation of the term may be  open or approximate to various
>>>> stakeholders due to lack of common definitions and glossary.
>>>>
>>>>
>>>> We already have a glossary page
>>>> https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
>>>> But it is not very exhaustive yet.
>>>>
>>>> I was planning to go through the BPRB pages and prepare a list of all
>>>> technical terms used in various pages for the purpose of enriching
>>>> (extending) the glossary.
>>>>
>>>> I invite opinions on whether it is worth ?
>>>>
>>>> My Arguments in favour:
>>>>
>>>> (1) We need a common plane for definitions, if there is a disparity
>>> between
>>>>        author's interpretation of a business term and the reader's or
>>>>        reviewer's interpretation there shall be a communication gap.
>>>>
>>>> (2) For newbies it is a great resource  because it increases their
>>>>        knowledge as well as ability of understanding more
>> articles/pages.
>>>> (3) consistency of articles: if all authors/contributors use the same
>>>> terminology
>>>>        then the content created by them shall relate to each other in a
>>> more
>>>>        consistent manner.
>>>>
>>>> Implementation notes:
>>>> ----------------------------
>>>> currently we have our glossary in a flat list format with is the
>> easiest
>>>> way
>>>> to get started. However as the volume of terms and documentation
>>> increases
>>>> we shall also require to organise the glossary in a more methodical
>> way.
>>>> Some of the relevant standards are W3C standards like SKOS [1]  ,
>> OWL[2].
>>>> I am not sure if confluence has components that allow organising
>>> vocabulary
>>>> at this moment.
>>>>
>>>> Even if its' not there we can continue to enrich the Glossary / Vocab
>> in
>>> a
>>>> simple
>>>> manner (and later migrate/upgrade it).
>>>>
>>>>
>>>> References:
>>>> [1] https://www.w3.org/2004/02/skos/intro
>>>> [2] https://www.w3.org/2001/sw/wiki/OWL
>>>>

[Rajesh Mallah]

Thanks Jacques ,

noted

regds
mallah.




On Tue, Aug 29, 2017 at 6:33 PM, Jacques Le Roux <
[hidden email]> wrote:

> Rajesh,
>
> Something you want to avoid in Confluence titles are special characters.
>
> Confluence does not handle them well and so create URLs for the page like
> yours below.
>
> I replaced & by and and the page is now at https://cwiki.apache.org/confl
> uence/display/OFBIZ/ScratchPad+for+collecting+Terms+and+Acronyms
>
> It's under Home wich is fine for now because it's only a temporary page.
> Later we would want to move it directly under
> https://cwiki.apache.org/confluence/display/OFBIZ/Documentation
>
> HTH
>
> Jacques
>
>
>
> Le 29/08/2017 à 13:23, Rajesh Mallah a écrit :
>
>> Thanks for the kind words everyone.
>>
>> I already created a scratchpad
>>
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73635445
>>
>> it is my first page and i feel it got created in a wrong place.  :D
>>
>> request senior members to kindly relocate to a more suitable place.
>>
>> regds
>> mallah.
>>
>>
>>
>>
>>
>> On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
>> [hidden email]> wrote:
>>
>> +1 for the idea.
>>>
>>> Few More Suggestions:
>>>
>>> 1) Glossary of terms can also be bifurcated based on business processes
>>> or
>>> OFBiz components. For Example, inventory can have business terms like
>>> ATP,
>>> QOH, Back Order etc.
>>> 2) We can also incorporate business terminologies used in real world. So,
>>> people can relate those terms to the framework.
>>>
>>> Also, I would like to contribute to this glossary enrichment effort too.
>>>
>>> Thanks and Regards,
>>>
>>> Shivangi Tanwar
>>>
>>> On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <
>>> [hidden email]>
>>> wrote:
>>>
>>> I like the idea, +1.
>>>>
>>>> Thanks & Regards,
>>>> Devanshu Vyas.
>>>>
>>>> On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <[hidden email]
>>>> >
>>>> wrote:
>>>>
>>>> Hi ,
>>>>>
>>>>> We use many technical terms throughout the pages and articles but
>>>>> the interpretation of the term may be  open or approximate to various
>>>>> stakeholders due to lack of common definitions and glossary.
>>>>>
>>>>>
>>>>> We already have a glossary page
>>>>> https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
>>>>> But it is not very exhaustive yet.
>>>>>
>>>>> I was planning to go through the BPRB pages and prepare a list of all
>>>>> technical terms used in various pages for the purpose of enriching
>>>>> (extending) the glossary.
>>>>>
>>>>> I invite opinions on whether it is worth ?
>>>>>
>>>>> My Arguments in favour:
>>>>>
>>>>> (1) We need a common plane for definitions, if there is a disparity
>>>>>
>>>> between
>>>>
>>>>>        author's interpretation of a business term and the reader's or
>>>>>        reviewer's interpretation there shall be a communication gap.
>>>>>
>>>>> (2) For newbies it is a great resource  because it increases their
>>>>>        knowledge as well as ability of understanding more
>>>>>
>>>> articles/pages.
>>>
>>>> (3) consistency of articles: if all authors/contributors use the same
>>>>> terminology
>>>>>        then the content created by them shall relate to each other in a
>>>>>
>>>> more
>>>>
>>>>>        consistent manner.
>>>>>
>>>>> Implementation notes:
>>>>> ----------------------------
>>>>> currently we have our glossary in a flat list format with is the
>>>>>
>>>> easiest
>>>
>>>> way
>>>>> to get started. However as the volume of terms and documentation
>>>>>
>>>> increases
>>>>
>>>>> we shall also require to organise the glossary in a more methodical
>>>>>
>>>> way.
>>>
>>>> Some of the relevant standards are W3C standards like SKOS [1]  ,
>>>>>
>>>> OWL[2].
>>>
>>>> I am not sure if confluence has components that allow organising
>>>>>
>>>> vocabulary
>>>>
>>>>> at this moment.
>>>>>
>>>>> Even if its' not there we can continue to enrich the Glossary / Vocab
>>>>>
>>>> in
>>>
>>>> a
>>>>
>>>>> simple
>>>>> manner (and later migrate/upgrade it).
>>>>>
>>>>>
>>>>> References:
>>>>> [1] https://www.w3.org/2004/02/skos/intro
>>>>> [2] https://www.w3.org/2001/sw/wiki/OWL
>>>>>
>>>>>
>

[Rajesh Mallah]

Thanks Rishi ,

I was actually looking for a total node list . no probs shall create one and
your info shall quicken the traversal.

regds
mallah.



On Tue, Aug 29, 2017 at 6:12 PM, Rishi Solanki <[hidden email]>
wrote:

> +1 for the idea Rajesh.
>
> To answer your question, did you notice the child pages in the bottom?
>
> Here is quick reference;
> Page: Customer Relationship Management (CRM)
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73634368
> >
> Page: E-commerce
> <https://cwiki.apache.org/confluence/display/OFBIZ/E-commerce>
> Page: Financial Accounting and Reporting
> <https://cwiki.apache.org/confluence/display/OFBIZ/
> Financial+Accounting+and+Reporting>
> Page: Human Resources Management
> <https://cwiki.apache.org/confluence/display/OFBIZ/
> Human+Resources+Management>
> Page: Manufacturing
> <https://cwiki.apache.org/confluence/display/OFBIZ/Manufacturing>
> Page: Order Fulfillment Process
> <https://cwiki.apache.org/confluence/display/OFBIZ/
> Order+Fulfillment+Process>
> Page: Party <https://cwiki.apache.org/confluence/display/OFBIZ/Party>
> Page: Product Information Management (PIM)
> <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=46631782
> >
> Page: Sales Order Management
> <https://cwiki.apache.org/confluence/display/OFBIZ/Sales+Order+Management>
> Page: Supply Chain Planning
> <https://cwiki.apache.org/confluence/display/OFBIZ/Supply+Chain+Planning>
> Page: Warehouse Management
> <https://cwiki.apache.org/confluence/display/OFBIZ/Warehouse+Management>
>
>
> Rishi Solanki
> Sr Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: [phone]
> http://www.hotwaxsystems.com
> www.hotwax.co
>
> On Tue, Aug 29, 2017 at 5:32 PM, Rajesh Mallah <[hidden email]>
> wrote:
>
> > can someone conversant with confluence/wiki point me to list of *all*
> pages
> > created under
> >
> > https://cwiki.apache.org/confluence/display/OFBIZ/
> > Business+Process+Reference+Book
> >
> > else i have to create the list in the hard way (manually).
> >
> > regds
> > mallah.
> >
> >
> > On Tue, Aug 29, 2017 at 5:27 PM, Ankit Joshi <
> > [hidden email]>
> > wrote:
> >
> > > +1 for the Idea.
> > >
> > > Thanks & Regards,
> > > Ankit Joshi
> > >
> > >
> > > On Tue, Aug 29, 2017 at 5:13 PM, Rajesh Mallah <
> [hidden email]>
> > > wrote:
> > >
> > > > Hi Shivangi ,
> > > >
> > > > pls find replies inline.
> > > >
> > > > On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
> > > > [hidden email]> wrote:
> > > >
> > > > > +1 for the idea.
> > > > >
> > > > > Few More Suggestions:
> > > > >
> > > > > 1) Glossary of terms can also be bifurcated based on business
> > processes
> > > > or
> > > > > OFBiz components. For Example, inventory can have business terms
> like
> > > > ATP,
> > > > > QOH, Back Order etc.
> > > > > 2) We can also incorporate business terminologies used in real
> world.
> > > So,
> > > > > people can relate those terms to the framework.
> > > > >
> > > > >
> > > > Both the above requirements are covered in a generic manner via
> various
> > > > relationship
> > > > mechanism in  SKOS system , I am hopeful confluence would have some
> > > plugin
> > > > that
> > > > allows to leverage on that or some related technology or standard for
> > > > maintaining vocabs
> > > > and semantic relations between terms  . ( I  would explore at some
> > point
> > > )
> > > >
> > > > SKOS article ( 2-3 mins reading time ).
> > > >  https://en.wikipedia.org/wiki/Simple_Knowledge_
> > > > Organization_System#Concepts
> > > >
> > > > I also observe that certain SKOS concept are already in use in
> Catalog
> > >
> > > > Thesaurus application.
> > > >
> > > > Also, I would like to contribute to this glossary enrichment effort
> > too.
> > > > >
> > > >
> > > > Sure ! & thanks  , its being done as a Wiki page only. As a matter of
> > > fact
> > > > contribution and enrichment to definitions should done by banking
> upon
> > > > existing definitions and on knowledge which can be borrowed on
> reliable
> > > > sources . (no point re-inventing , definitions , we have to put it in
> > > > context
> > > > of ofbiz only ).
> > > >
> > > >
> > > > regds
> > > > mallah.
> > > >
> > > >
> > > > >
> > > > > Thanks and Regards,
> > > > >
> > > > > Shivangi Tanwar
> > > > >
> > > > > On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <
> > > > [hidden email]>
> > > > > wrote:
> > > > >
> > > > > > I like the idea, +1.
> > > > > >
> > > > > > Thanks & Regards,
> > > > > > Devanshu Vyas.
> > > > > >
> > > > > > On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <
> > > > [hidden email]>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi ,
> > > > > > >
> > > > > > > We use many technical terms throughout the pages and articles
> but
> > > > > > > the interpretation of the term may be  open or approximate to
> > > various
> > > > > > > stakeholders due to lack of common definitions and glossary.
> > > > > > >
> > > > > > >
> > > > > > > We already have a glossary page
> > > > > > > https://cwiki.apache.org/confluence/display/OFBENDUSER/
> Glossary
> > > > > > > But it is not very exhaustive yet.
> > > > > > >
> > > > > > > I was planning to go through the BPRB pages and prepare a list
> of
> > > all
> > > > > > > technical terms used in various pages for the purpose of
> > enriching
> > > > > > > (extending) the glossary.
> > > > > > >
> > > > > > > I invite opinions on whether it is worth ?
> > > > > > >
> > > > > > > My Arguments in favour:
> > > > > > >
> > > > > > > (1) We need a common plane for definitions, if there is a
> > disparity
> > > > > > between
> > > > > > >       author's interpretation of a business term and the
> reader's
> > > or
> > > > > > >       reviewer's interpretation there shall be a communication
> > gap.
> > > > > > >
> > > > > > > (2) For newbies it is a great resource  because it increases
> > their
> > > > > > >       knowledge as well as ability of understanding more
> > > > > articles/pages.
> > > > > > >
> > > > > > > (3) consistency of articles: if all authors/contributors use
> the
> > > same
> > > > > > > terminology
> > > > > > >       then the content created by them shall relate to each
> other
> > > in
> > > > a
> > > > > > more
> > > > > > >       consistent manner.
> > > > > > >
> > > > > > > Implementation notes:
> > > > > > > ----------------------------
> > > > > > > currently we have our glossary in a flat list format with is
> the
> > > > > easiest
> > > > > > > way
> > > > > > > to get started. However as the volume of terms and
> documentation
> > > > > > increases
> > > > > > > we shall also require to organise the glossary in a more
> > methodical
> > > > > way.
> > > > > > > Some of the relevant standards are W3C standards like SKOS
> [1]  ,
> > > > > OWL[2].
> > > > > > > I am not sure if confluence has components that allow
> organising
> > > > > > vocabulary
> > > > > > > at this moment.
> > > > > > >
> > > > > > > Even if its' not there we can continue to enrich the Glossary /
> > > Vocab
> > > > > in
> > > > > > a
> > > > > > > simple
> > > > > > > manner (and later migrate/upgrade it).
> > > > > > >
> > > > > > >
> > > > > > > References:
> > > > > > > [1] https://www.w3.org/2004/02/skos/intro
> > > > > > > [2] https://www.w3.org/2001/sw/wiki/OWL
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

[Michael Brohl-3]

I've moved the page under "Documentation" where it belongs.

Please do not put pages, temporary or not, in the root of our wiki. We
are working on a user friendly structure and if new pages are simply put
in root, they soon clutter the look of the sidebar.

Thanks,

Michael

Am 29.08.17 um 15:03 schrieb Jacques Le Roux:

> Rajesh,
>
> Something you want to avoid in Confluence titles are special characters.
>
> Confluence does not handle them well and so create URLs for the page
> like yours below.
>
> I replaced & by and and the page is now at
> https://cwiki.apache.org/confluence/display/OFBIZ/ScratchPad+for+collecting+Terms+and+Acronyms
>
> It's under Home wich is fine for now because it's only a temporary
> page. Later we would want to move it directly under
> https://cwiki.apache.org/confluence/display/OFBIZ/Documentation
>
> HTH
>
> Jacques
>
>
> Le 29/08/2017 à 13:23, Rajesh Mallah a écrit :
>> Thanks for the kind words everyone.
>>
>> I already created a scratchpad
>>
>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73635445 
>>
>>
>> it is my first page and i feel it got created in a wrong place. :D
>>
>> request senior members to kindly relocate to a more suitable place.
>>
>> regds
>> mallah.
>>
>>
>>
>>
>>
>> On Tue, Aug 29, 2017 at 4:44 PM, Shivangi Tanwar <
>> [hidden email]> wrote:
>>
>>> +1 for the idea.
>>>
>>> Few More Suggestions:
>>>
>>> 1) Glossary of terms can also be bifurcated based on business
>>> processes or
>>> OFBiz components. For Example, inventory can have business terms
>>> like ATP,
>>> QOH, Back Order etc.
>>> 2) We can also incorporate business terminologies used in real
>>> world. So,
>>> people can relate those terms to the framework.
>>>
>>> Also, I would like to contribute to this glossary enrichment effort
>>> too.
>>>
>>> Thanks and Regards,
>>>
>>> Shivangi Tanwar
>>>
>>> On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas
>>> <[hidden email]>
>>> wrote:
>>>
>>>> I like the idea, +1.
>>>>
>>>> Thanks & Regards,
>>>> Devanshu Vyas.
>>>>
>>>> On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah
>>>> <[hidden email]>
>>>> wrote:
>>>>
>>>>> Hi ,
>>>>>
>>>>> We use many technical terms throughout the pages and articles but
>>>>> the interpretation of the term may be  open or approximate to various
>>>>> stakeholders due to lack of common definitions and glossary.
>>>>>
>>>>>
>>>>> We already have a glossary page
>>>>> https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
>>>>> But it is not very exhaustive yet.
>>>>>
>>>>> I was planning to go through the BPRB pages and prepare a list of all
>>>>> technical terms used in various pages for the purpose of enriching
>>>>> (extending) the glossary.
>>>>>
>>>>> I invite opinions on whether it is worth ?
>>>>>
>>>>> My Arguments in favour:
>>>>>
>>>>> (1) We need a common plane for definitions, if there is a disparity
>>>> between
>>>>>        author's interpretation of a business term and the reader's or
>>>>>        reviewer's interpretation there shall be a communication gap.
>>>>>
>>>>> (2) For newbies it is a great resource  because it increases their
>>>>>        knowledge as well as ability of understanding more
>>> articles/pages.
>>>>> (3) consistency of articles: if all authors/contributors use the same
>>>>> terminology
>>>>>        then the content created by them shall relate to each other
>>>>> in a
>>>> more
>>>>>        consistent manner.
>>>>>
>>>>> Implementation notes:
>>>>> ----------------------------
>>>>> currently we have our glossary in a flat list format with is the
>>> easiest
>>>>> way
>>>>> to get started. However as the volume of terms and documentation
>>>> increases
>>>>> we shall also require to organise the glossary in a more methodical
>>> way.
>>>>> Some of the relevant standards are W3C standards like SKOS [1]  ,
>>> OWL[2].
>>>>> I am not sure if confluence has components that allow organising
>>>> vocabulary
>>>>> at this moment.
>>>>>
>>>>> Even if its' not there we can continue to enrich the Glossary / Vocab
>>> in
>>>> a
>>>>> simple
>>>>> manner (and later migrate/upgrade it).
>>>>>
>>>>>
>>>>> References:
>>>>> [1] https://www.w3.org/2004/02/skos/intro
>>>>> [2] https://www.w3.org/2001/sw/wiki/OWL
>>>>>
>

[Michael Brohl-3]

+1

Great initiative, thank you, Rajesh!

Regards,

Michael


Am 29.08.17 um 12:07 schrieb Rajesh Mallah:

> Hi ,
>
> We use many technical terms throughout the pages and articles but
> the interpretation of the term may be  open or approximate to various
> stakeholders due to lack of common definitions and glossary.
>
>
> We already have a glossary page
> https://cwiki.apache.org/confluence/display/OFBENDUSER/Glossary
> But it is not very exhaustive yet.
>
> I was planning to go through the BPRB pages and prepare a list of all
> technical terms used in various pages for the purpose of enriching
> (extending) the glossary.
>
> I invite opinions on whether it is worth ?
>
> My Arguments in favour:
>
> (1) We need a common plane for definitions, if there is a disparity between
>        author's interpretation of a business term and the reader's or
>        reviewer's interpretation there shall be a communication gap.
>
> (2) For newbies it is a great resource  because it increases their
>        knowledge as well as ability of understanding more articles/pages.
>
> (3) consistency of articles: if all authors/contributors use the same
> terminology
>        then the content created by them shall relate to each other in a more
>        consistent manner.
>
> Implementation notes:
> ----------------------------
> currently we have our glossary in a flat list format with is the easiest way
> to get started. However as the volume of terms and documentation increases
> we shall also require to organise the glossary in a more methodical way.
> Some of the relevant standards are W3C standards like SKOS [1]  , OWL[2].
> I am not sure if confluence has components that allow organising vocabulary
> at this moment.
>
> Even if its' not there we can continue to enrich the Glossary / Vocab in a
> simple
> manner (and later migrate/upgrade it).
>
>
> References:
> [1] https://www.w3.org/2004/02/skos/intro
> [2] https://www.w3.org/2001/sw/wiki/OWL
>