Browse wiki

en: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]]'''.

en:'''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.

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]]'''.

'''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.

[[SMW::off]] <tr id="ac:hasServiceAccessPoint"> <td id="Service_Access_Point" width="100px" style="text-align:right; vertical-align:bottom;background:#EEE; border-bottom: 1px solid #CCC; padding:1.1em 0.5em 0.5em 0.5em;">Concept Name:</td> <td style="text-align:left; vertical-align:bottom;background:#EEE;border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:1.1em 0.5em 0.5em 0.5em;">'''[[ac:hasServiceAccessPoint]]'''</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Normative URI</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">http://rs.tdwg.org/ac/terms/hasServiceAccessPoint</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Label</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Service Access Point</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Definition</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">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]]'''.</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Defined By</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:hasServiceAccessPoint</td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;"> </td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">'''Required: ''' No — '''Repeatable: ''' No<span class="debug-required-repeatable" style="display:none;">http://rs.tdwg.org/ac/terms/hasServiceAccessPoint, </span></td> </tr><tr> <td style="text-align:right;vertical-align:top;background:#EEE;border-right:1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">Notes:</td> <td style="border-right: 1px solid #CCC; border-bottom: 1px solid #CCC; padding:0.5em;">'''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.</td></tr>[[SMW::on]]