Difference between revisions of "SV ServiceIdentification"
From Earth Science Information Partners (ESIP)
Line 20: | Line 20: | ||
{{template:isoOrderingFooter}} | {{template:isoOrderingFooter}} | ||
− | |||
− | |||
− | |||
[[Category:ISO_19119]] | [[Category:ISO_19119]] |
Revision as of 17:59, December 21, 2016
Elements | Definition and Recommended Practice | Examples | ||
---|---|---|---|---|
1 | citation | 1 | Citation for the resource, includes name, publication date, identifiers, originators and publishers. | Example is needed |
2 | abstract | 1 | Brief narrative summary of the resource contents. Include summary information on general content and features; resource applications: GIS, CAD, image, database; geographic coverage: county/city name; time period of content: begin and end date or single date; and special data characteristics or limitations. | Example is needed |
3 | purpose | 0..* | Summary of intentions for which the resource was developed. | Example is needed |
4 | credit | 0..* | Recognition of those who contributed to the dataset. Do not include URLs here. Provide full citations in MD_AssociatedResource section. | Example is needed |
5 | status | 0..* | Status of resource development. Most common status values to use are 'completed', 'ongoing', 'planned' or 'underDevelopment'. Highly recommend populating this field. | Example is needed |
6 | pointOfContact | 0..* | Individuals and/or organizations available for questions about the resource. Use roleCode="pointOfContact". This should be a person at an archive or the originator of the resource. Provide contact details, such address, phone and email. | Example is needed |
14 | resourceMaintenance | 0..* | Information about the frequency, scope, and responsible party for the updating of the resource. | Example is needed |
15 | graphicOverview | 0..* | A small image that exemplifies the collective resource. The graphic file should be less than 500KB and 1000x1000 pixels. Provide URL to an image that can be rendered in browsers. | Example is needed |
16 | resourceFormat | 0..* | Information about the formats of the resource. This is independant of the distribution details and is useful to provide when the resource has a status of 'planned' or 'underDevelopment'. | Example is needed |
17 | descriptiveKeywords | 0..* | Commonly used words or phrases which describe the dataset. Optionally, the keyword type and a citation for the authoritative or registered resource of the keywords are also provided. | Example is needed |
18 | resourceSpecificUsage | 0..* | Basic information about specific application(s) for which the resource(s) has been or is being used by different users. | Example is needed |
19 | resourceConstraints | 0..* | The limitations or constraints on the use of or access to the resource. | Example is needed |
20 | associatedResource | 0..* | The citations and identifiers of associated resources, such as projects and documents. | Example is needed |
1 | serviceType | 1 | A term for describing the type of service. For example 'discovery', 'view', 'download', 'transformation', or 'invoke'. | Example is needed |
2 | serviceTypeVersion | 0..* | The service type version. For example, we may only be interested in OGC Catalogue V1.1 services. If the version is maintained as a separate attribute, users can easily search for all services of a type regardless of the version | Example is needed |
3 | accessProperties | 0..* | Service access information such as fees, availability, ordering instructions, turnaround time, etc. | Example is needed |
4 | couplingType | 0..* | The type of coupling between service and associated data. | Example is needed |
5 | coupledResource | 0..* | A more detailed description of the data coupling in the case of tightly coupled services. | Example is needed |
6 | operatedDataset | 0..* | A reference to the dataset on which the service operates. | Example is needed |
7 | profile | 0..* | Definition needed | Example is needed |
8 | serviceStandard | 0..* | Definition needed | Example is needed |
9 | containsOperations | 0..* | Definition needed | Example is needed |
10 | operatesOn | 0..* | Definition needed | Example is needed |
11 | containsChain | 0..* | Definition needed | Example is needed |