Transcript Energy Scenario Architecture Implementation Pilot AIP-3 Lionel Menard – Mines ParisTech Agenda • • • • • • Communication matter Brief GCI recap End To End Use Cases Energy Scenario Update of GENESIS.

Energy Scenario
Architecture Implementation Pilot AIP-3
Lionel Menard – Mines ParisTech
Agenda
•
•
•
•
•
•
Communication matter
Brief GCI recap
End To End Use Cases
Energy Scenario
Update of GENESIS platform
Open discussion
– Web Services needed for the scenario (Mines ParisTech) -Deploy resource– Metadata, Catalogue and Registration (Mines ParisTech and GENESIS)-"Register
resource-and -Harvest & Query via GEOSS Clearinghouse– Test and Deploy Web Services (Mines ParisTech) -Test Service- -Deploy Service– Interface Client development (GENESIS and Mines ParisTech) -Present Service-, Interact with Service-, -Exploit Data Visually and Analytically– Construct and Deploy Workflow -Construct and Deploy Workflow-
• Actions list (TBD)
Communication Plan
• AIP-3 Collaborative Workspace
– http://sites.aip3.ogcnetwork.net/home/
– http://sites.google.com/a/aip3.ogcnetwork.net/home/home
/energy
• Mailing-List
– Could you register to the Energy AIP-3 Mailing-List
– https://lists.opengeospatial.org/mailman/listinfo/aip_energ
y
– To post a message to all the list members, send email to
[email protected]
• Web Conferencing System
– Web-Ex for Plenary
– Dim-Dim for Energy Scenario
List of participants
Jef Vanbockryck
<[email protected]>
Simone Gianfranceschi
<[email protected]>
Mariarosaria Barone
<[email protected]>
Massimiliano Fanciulli
<[email protected]>
Benoit Gschwind
<[email protected]>
Thierry Ranchin
<[email protected]>
Lucien Wald
<[email protected]>,
Steven Smolders
<[email protected]>
Cristiano Fugazza
<[email protected]>
Bertrand De Longueville
<[email protected]>
Stephane Bonnot
<[email protected]>
Didier Beloin-Saint-Pierre
<[email protected]>
Philippe Blanc
<[email protected]>
Marc Gilles
<[email protected]>
Jean-Louis Fondere
<[email protected]>
Isabelle Blanc
<[email protected]>
Cyril Grassin
<[email protected]>
Christian Alegre
<[email protected]>
User
Applications
Main GEO
Web Site
links to
Web browser
accesses
links to
GEOSS
Common
Infrastructure
accesses
registry items
Unregistered
Community Resources
GEO
Web Portal
GEO
GEOWeb
WebPortal
Portal
Registries
links to
GEOSS
Registry
query
clients
GEOSS
Standards and
Interoperability
Registry
RSS
searches
Component and
Service Registry
references
GEONETCast
Web pages
accesses
service
descriptions
GEOSS
GEOSS
GEOSS
Clearinghouse
Clearinghouse
Clearinghouse
Catalog
query
clients
catalogues all
Registration
clients
Best Practices
Wiki
User Requirements
Registry
references
Documents
Clearinghouse
provides means
to connect to
registered
services via
metadata
Registered components and services
Websites/
Services
Portals
(Components)
Data and
Service
Catalogues
This
useResources
case
describes
the
conditions
and
steps
for
exploitation
Register,
inResources
the
GEOSS
Standards
and
Interoperability
Registry
Deploy
Service
Harvest
Search
for
Provider
and
cases
Query
covers
tests
for
Metadata
via
its
making
service
GEOSS
in conditions
GEOSS.
via
information
GEOSS
using
Clearinghouse(s)
This
a
proper
Clearinghouse.
about
use
case
Test
afor
GEOSS
or
identifies
tool
Community
This
use
This
use
case
describes
aims
at use
capturing
the
many
ofthe
the
alternative
aspects
and
steps
that
approaches
are
portals
common
toand
toin
Client
Applications
of
datasets
served
through
Web
Services
and
(SIR),
new
and
recommended
interoperability
arrangements)
as
resource
many
discovered
case
Catalog(s).
describes
ofdeploy
the
known
in
This
aspects
the
the
use
toGEOSS
the
steps
case
that
GEOSS
are,
for
describes
CSR.
or
community,
should
thebe,
and/or
conditions
common
and
querying
“findable”
and
tocan
all
steps
service
through
or foror
application
OGC
design,
Web
Services
clients
and
to
execute
(WFS,
present
SOS,
aharvesting
the
workflow.
GEOSS
WCS,
The
WMS).
User
workflow
with
These
the
common
reachable
be
online
protocols
as
used
within
GEOSS.
well
as
utilized
standards.
This
use
case
covers
the
action
of
a GEOSS
multiple
content
portals
and
metadata
Web
Clearinghouse,
application
Services
from
interface
clients
community
by
toby
Implementation
support
catalogs
registering
the(BPEL),
or
GEOSS
services
the
Specifications.
resource
user
via in
adirectly
services
aspects
described
are
and
in
primarily
Business
alerts
assome
returned
Execution
ofeither
the
Language
parameters
the
GEOSS
and
Clearinghouse(s)
data
Sensor
structures
closing
the
loop
on
interoperability
practices
and
arrangements
with the
GEOSS
searching
GEOSS
Clearinghouse.
for
resources
CSR
orofregistering
interest
via
a user’s
community
the
GEOSS
catalog/metadata
and/or
used
Markup
inCommunity
operation
Language
requests
(SensorML),
Catalog(s)
andper
responses.
or the
any
other
search
script
language.
criteria.
(standard
otherwise)
that has
have
been implemented
for GEOSS.
service in and
Clearinghouse(s)
which
the
or resource
Community
Catalog(s).
already
been registered.
End-to-End Use Cases (Patterns)
Existing, Re-usable and New Components
• Energy Community Portal (www.webservice-energy.com)
– Several Resources Deployed (WSDL W3C Services)
– JSR-168 Portlets (Liferay) (project.mesor.org)
– Support for Catalogs and Metadata (INSPIRE & WAF)
– Register in the GEOSS CSR (Catalog & Service Registry)
• New for AIP-3
– Host Solar Radiation & Impact assessment databases
– Deploy OGC WMS & WPS
– Host OGC Catalog and Metadata
– Convert existing W3C Services to OGC