Difference between revisions of "ac:hasServiceAccessPoint"

Revision as of 11:32, 15 November 2012 (view source) Andreas Plank (Talk | contribs) m (Concept type) ← Older edit		Revision as of 22:57, 9 November 2013 (view source) BobMorris (Talk | contribs) m (provide "is defined by" link) Newer edit →
Line 5:		Line 5:
	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}}#{{PAGENAME}} <!-- for ac at least, this pagename is also the term name -->
	|concept type=property		|concept type=property
	|hidden notes=// Repeatable = Yes		|hidden notes=// Repeatable = Yes

---

Revision as of 22:57, 9 November 2013

Scheme: Audubon Core Development 
Collections: Audubon Core Management Vocabulary , Audubon Core Layer 1 

Service Access Point No type definition was found for "hasServiceAccessPoint" in the ac import. URI: http://rs.tdwg.org/ac/terms/hasServiceAccessPoint is defined by http://terms.tdwg.org/wiki/Audubon_Core_Term_List#ac:hasServiceAccessPoint

RDF feed | Browse properties | SMW-prop.

Search for values

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