Difference between revisions of "ac:hasServiceAccessPoint"
From TDWG Terms Wiki
(fixed newline issue) |
|||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | __NOINDEX__ | ||
| + | <span style="background-color:#ffc; padding:5px; color:#f00;border:1px solid #f00;">'''Warning''': This is not the current version of this document. It is kept for archival purposes. For up-to-date information, go to https://tdwg.github.io/ac/termlist/#ac_hasServiceAccessPoint</span><br /><br /> | ||
| + | |||
| + | |||
{{Concept | {{Concept | ||
| − | + | |label=Service Access Point | |
| − | + | |definition=In a chosen serialization (RDF, XML Schema, etc.) the potentially multiple service access points (e.g. for different resolutions of an image) might be provided in a referenced or in a nested object. This property identifies one such access point. That is, each of potentially multiple values of hasServiceAccessPoint identifies a set of representation-dependent metadata using the properties defined under the section '''[[Audubon Core Term List#Service Access Point Vocabulary|Service Access Point Vocabulary]]'''. | |
| − | + | |notes='''Audubon Core:''' Some serializations may flatten the model of service-access points by (a) dropping ac:hasServiceAccessPoint, ac:variant and ac:variantDescription, (b) repeating the properties of the Service Access Point Vocabulary and prefixing them with values of ac:variant. If such a flat serialization is necessary for services, we recommend to select from among terms of the form "AB" where "A" is one of thumbnail, trailer, lowerQuality, mediumQuality, goodQuality, bestQuality, offline and "B" is one of AccessURI, Format, Extent, FurtherInformationURL, LicensingException, ServiceExpectation (example: thumbnailAccessURI). | |
| − | + | ||
| − | + | ||
Implementers in specific constraint languages such as XML Schema or RDF may wish to make Access URI and perhaps dcterms:format mandatory on instances of the service access point. | Implementers in specific constraint languages such as XML Schema or RDF may wish to make Access URI and perhaps dcterms:format mandatory on instances of the service access point. | ||
| − | + | |is defined by={{ACTERMLIST}}#ac:hasServiceAccessPoint <!-- for ac at least, this pagename is also the term name --> | |
| + | |concept type=property | ||
| + | |hidden notes=// Repeatable = Yes | ||
}} | }} | ||
{{Concept scheme relation | {{Concept scheme relation | ||
| − | |scheme=Audubon Core | + | |scheme=Audubon Core Development |
}} | }} | ||
{{Concept relation | {{Concept relation | ||
Latest revision as of 13:04, 5 March 2020
Warning: This is not the current version of this document. It is kept for archival purposes. For up-to-date information, go to https://tdwg.github.io/ac/termlist/#ac_hasServiceAccessPoint
| Service Access Point No type definition was found for "hasServiceAccessPoint" in the ac import.
|
Search for values  |
Notes: Audubon Core: Some serializations may flatten the model of service-access points by (a) dropping ac:hasServiceAccessPoint, ac:variant and ac:variantDescription, (b) repeating the properties of the Service Access Point Vocabulary and prefixing them with values of ac:variant. If such a flat serialization is necessary for services, we recommend to select from among terms of the form "AB" where "A" is one of thumbnail, trailer, lowerQuality, mediumQuality, goodQuality, bestQuality, offline and "B" is one of AccessURI, Format, Extent, FurtherInformationURL, LicensingException, ServiceExpectation (example: thumbnailAccessURI).
Implementers in specific constraint languages such as XML Schema or RDF may wish to make Access URI and perhaps dcterms:format mandatory on instances of the service access point.
