Facet Based Resource Model

Facets

Access Point Facet

The goal of this facet is expected to capture information on “access points” for a resource, i.e. any endpoint to interact with the resource via a known protocol.

entryName	String	An unique identifier
endpoint	URI	The URI which identify the endpoint of a resource
protocol	String	The high-level protocol used by the access point. The String could contains the version if needed. E.g. WMS not http which is already contained in URI.
description	String	.....
authorizationValue	String	Contains authorization information. E.g: a token, username:password. By relying on schema it should be sufficient to capture also whether the content is encrypted or not
authorizationSchema	URI	....
propertiesValue	String	This can be an arbitrarily complex element whose "structure" is defined by the associated schema
propertiesSchema	URI	....

Contact Facet

The goal of this facet is expected to capture contact information

name	String	TBD Contains Name and Surname or we add a new Field
eMail	Valid eMail address	An RFC‑822 compliant email address. (ere you can find a very complex regular expression http://www.ex-parrot.com/~pdw/Mail-RFC822-Address.html for email address validation) TBD LIST?
website	URL	TBD LIST?
address	String	TBD LIST?
phone	String	TBD LIST?

Identification Facet

The goal of this facet is to collect information on Identifiers that can be attached to a resource.

value	String	The identifier. E.g. http://fr.dbpedia.org/resource/Thunnus de305d54-75b4-431b-adb2-eb6b9e546014
type	Enumeration	The typology of identifier. E.g. URI, DOI, IRI, URL, URN, UUID;
isPersistent	boolean	To indicate if the Identifier is persistent or not.

Relations

The following relations (extending the relatedTo) have been identified and defined:

• callsFor: Service to Service
• dependsOn: Software to Software
• managedBy: Hosting Node to Site
• manages: Service to Dataset
• poweredBy: Hosting Node to Software
• requires: Software to Service

Resource Profiles

The following resources have been identified:

• Actor
• Configuration
• Dataset
  • Concrete Dataset
• Service
  • Abstract Service
  • E-Service
  • Hosting Node
• Software

Service

Service Profile

Facets
name	multiplicity	description
Identification	1..n
Relations

Abstract Service

Abstract Service Profile

Facets
facet	multiplicity	description
Extends Service

E-Service

E-Service Profile

Facets
facet	multiplicity	description
Extends Service
Access Point	1..n
Relations
runs (out)	0..n	A reference to the Software artifact the E-Service results from.
use (out)	0..n	A reference to any other E-Service, the E-Service instance is invoking.
hosts (in)	1	An inverse reference stemming from the Hosting Node that is operating the E-Service.

Hosting Node

Extends Service

Hosting Node Profile

Facets
facet	multiplicity	description
Extends Service