Re: glossary enrichment proposal

[Michael Brohl]

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



Thanks,

Michael

Am 29.08.17 um 15:03 schrieb Jacques Le Roux:

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.

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 <
shivangi.tan...@hotwaxsystems.com> wrote:

+1 for the idea.

Few More Suggestions:


QOH, Back Order etc.

people can relate those terms to the framework.



Thanks and Regards,

Shivangi Tanwar


wrote:

1) Glossary of terms can also be bifurcated based on business processes or OFBiz components. For Example, inventory can have business terms like ATP, 2) We can also incorporate business terminologies used in real world. So, Also, I would like to contribute to this glossary enrichment effort too. On Tue, Aug 29, 2017 at 4:14 PM, Devanshu Vyas <vyas.devansh...@gmail.com>

I like the idea, +1.

Thanks & Regards,
Devanshu Vyas.


wrote:

On Tue, Aug 29, 2017 at 3:37 PM, Rajesh Mallah <mallah.raj...@gmail.com>

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

smime.p7s
Description: S/MIME Cryptographic Signature