Difference between revisions of "ac:hasServiceAccessPoint"
From TDWG Terms Wiki
(transfer of correction from normative to atomized) |
|||
| Line 3: | Line 3: | ||
| label = Access Point | | label = Access Point | ||
| label = Service Access Point | | 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 | + | | 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 = <b>Audubon Core:</b> 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). | | notes = <b>Audubon Core:</b> 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). | ||
Revision as of 07:36, 15 October 2012
| Service Access Point No type definition was found for "hasServiceAccessPoint" in the ac import.
|
RDF feed | Browse properties | Concept type not set. A property page exists already. Please set “Concept type = property”. |
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.
