Facet Based Resource Model
Contents |
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 maybe also middle name and title (Dr. Mr.) or we add a new fields |
| Valid eMail address | An RFC‑822 compliant email address.
(At http://www.ex-parrot.com/~pdw/Mail-RFC822-Address.html you can find a very complex regular expression for validation) | |
| website | URL | ... |
| address | String | ... |
| phone | String | ... |
Coverage Facet
The goal of this facet is to collect any extent-related information.
| spatialValue | String | ... |
| spatialSchema | URI | ... |
| temporalValue | String | ... |
| temporalSchema | URI | ..... |
CPU Facet
The goal of this facet is to describe CPU information. //TODO to be reviewed
| modelName | String | ... |
| vendor | String | ... |
| clockSpeed | String | ... |
Descriptive Metadata Facet
The goal of this facet is to collect any descriptive metadata about the resource.
| value | String | .... E.g. XML Blob |
| schema | URI | ... |
Event Facet
The goal of this facet is to collect any descriptive metadata about the resource.
| type | String | ... |
| typeSchema | URI | ... |
| date | String | ... |
| dateSchema | URI | ... |
Functionality Related Facet
The goal of this facet is to capture what are the facilities supported (Challenging because of the different audiences) Something very "poor" ... we can have a look at WPS spec
| name | String | ... |
| description | String | ... |
| input | String | ... |
| output | String | ... |
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. |
IP Info Facet
//TO BE RENAMED ??? The goal of this facet is to capture IP information
| IPAddress | String | ... |
| mask | String | ... |
| broadcastAddress | String | ... |
Regular expression to validate different IPv4 addresses are available at: http://www.regextester.com/22 https://www.safaribooksonline.com/library/view/regular-expressions-cookbook/9780596802837/ch07s16.html
Both IPv4 and IPv6: http://stackoverflow.com/questions/53497/regular-expression-that-matches-valid-ipv6-addresses
License Facet
The goal of this facet is to .....
| value | String | ... |
| schema | URI | ... |
Memory Facet
The goal of this facet is to .....
| size | Long | ... |
| used | Long | ... |
| unit | String | ... |
Persistent Memory Facet
Subclass of Memory Facet
TBD if instead of subclassing is better subclassing ConsistOf relation of reintroduce purpose in relation or header
Volatile Memory Facet
Subclass of Memory Facet
TBD if instead of subclassing is better subclassing ConsistOf relation of reintroduce purpose in relation or header
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
Actor
| Facets | ||
|---|---|---|
| name | multiplicity | description |
| Contact | 1..n | |
| Relations | ||
Configuration
Dataset
Concrete Dataset
Service
| Facets | ||
|---|---|---|
| name | multiplicity | description |
| Identification | 1..n | |
| Relations | ||
Abstract Service
| Facets | ||
|---|---|---|
| facet | multiplicity | description |
| Extends Service | ||
E-Service
| 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
| Facets | ||
|---|---|---|
| facet | multiplicity | description |
| Extends Service | ||
