-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
107 lines (87 loc) · 4.87 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
<link href='https://fonts.googleapis.com/css?family=Architects+Daughter' rel='stylesheet' type='text/css'>
<link rel="stylesheet" type="text/css" href="stylesheets/stylesheet.css" media="screen">
<link rel="stylesheet" type="text/css" href="stylesheets/github-light.css" media="screen">
<link rel="stylesheet" type="text/css" href="stylesheets/print.css" media="print">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<title>The Open-GDSN initiative by open-gdsn</title>
</head>
<body>
<header>
<div class="inner">
<h1>Open-GDSN</h1>
<h2>A soon to be launched attempt to create a open and free<a href="#1">¹</a> implementation in java.</h2>
<a href="https://github.com/open-gdsn" class="button"><small>Follow me on</small> GitHub</a>
</div>
</header>
<div id="content-wrapper">
<div class="inner clearfix">
<section id="main-content">
<h3>
<a id="open-gdsn" class="anchor" href="#open-gdsn" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>open-gdsn</h3>
<p>Yes, it really is a soon to be launched attempt to create a open and free<a href="#1">¹</a> implementation in java and xml of GDSN related 'things'.</p>
<p>Initially it will consist of just a <a href="open-gdsn">core project</a>, focussing on providing 'better' standards in the sence that they can be more effectively used in a technical (=executable) way
<ul>
<li>All GDSN Global validation rules in a Schematron annotated set of XSD's (including conditionally required fields)</li>
<li>Checks against codelists and/or allowed values</li>
</ul>
</p>
<p>Later on, it could be that this 'better standard' will be incorporated in a semi-end-user oriented framework with a api's to communicate with existing systems like
<ul>
<li>DataSource client (non-ui) for communicating with a certified SourceDataPool that supports the GDSN flow of messages</li>
<li>DataRecipient client (non-ui) for communicating with a certified RecipientDataPool that supports the GDSN flow of messages</li>
</ul>
or maybe even fully end-user oriented products
<ul>
<li>DataRecipient UI extending the DataRecipient client</li>
<li>DataSource UI extending the DataSource client</li>
</ul>
</p>
<p>Both clients should then of course be based on a the same code and should support:</p>
<ul>
<li>A view for all GDSN fields</li>
<li>Sending (DataSource) or receiving (DataRecipient) CIN messages</li>
<li>Sending (DataSource) CIP messages</li>
<li>Sending (DataRecipient) or receiving (DataSource) CIC messages</li>
<li>Sending (DataRecipient) CIS messages</li>
<li>Customize views based on target market</li>
<li>Customize validations (Global, targetMarket based, or fully custom)</li>
<li>Adding custom fields for internal use that won't get send to the datapool</li>
<li>Allowing to import data from a backoffice and add/populate additional fields before sending the data to the DataPool (merging) and keeping the added data in tact after an additional import</li>
<li>Running in a 'mixed mode' configuration so wholesale companies can receive data from the datapool and use that data to forward it to their retailers</li>
</ul>
<p>Of course all basic things you expect from a solution like this are supported</p>
<ul>
<li>searching</li>
<li>filtering</li>
<li>exporting</li>
<li>mass-update fields</li>
<li>status overview</li>
<li>error reporting </li>
</ul>
<h3>
<a id="future-ideas" class="anchor" href="#future-ideas" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Future ideas</h3>
<p>We think all the above is a great basis for a usable solution, but we certainly already have ideas for the future</p>
<ul>
<li>support for templating</li>
<li>saving/using custom filters</li>
<li>fully dynamic views based on e.g. GPC code</li>
<li>ability to send data to different datapools</li>
<li>support import mappings so custom formats can be uploaded</li>
</ul>
<h3>
<a id="goal" class="anchor" href="#goal" aria-hidden="true"><span aria-hidden="true" class="octicon octicon-link"></span></a>Goal</h3>
<p>The idea is that after an initial release of the DataSource and DataRecipient parts, a real full blown GSDSN compliant DataPool will be implemented too. One of the biggest challenges for this will be the costly <a href="https://www.drummondgroup.com/b2b-certified-products/b2b-standards/gdsn">Drummond certification</a> that is required by GS1. We are interested in anyone or (almost) any company that is interested in crowdfunding, sponsoring or helping out</p>
<p id="1">¹ for non commercial companies/usage </p>
</section>
</div>
</div>
</body>
</html>