Difference between revisions of "ac:hasServiceAccessPoint"
m (provide "is defined by" link) |
m (provide "is defined by" link) |
||
Line 10: | Line 10: | ||
}} | }} | ||
{{Concept scheme relation | {{Concept scheme relation | ||
− | |scheme=Audubon Core | + | |scheme=Audubon Core Development |
}} | }} | ||
{{Concept relation | {{Concept relation |
Revision as of 11:37, 15 November 2013
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.