{"id":353850,"date":"2024-10-20T01:00:08","date_gmt":"2024-10-20T01:00:08","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iso-191192016-tc\/"},"modified":"2024-10-26T01:10:49","modified_gmt":"2024-10-26T01:10:49","slug":"bs-en-iso-191192016-tc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iso-191192016-tc\/","title":{"rendered":"BS EN ISO 19119:2016 – TC"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
150<\/td>\n | European foreword Endorsement notice <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | 1\tScope 2\tConformance 2.1\tClaiming conformance 2.2\tGeneral 2.3\tEnterprise viewpoint 2.4\tComputational viewpoint <\/td>\n<\/tr>\n | ||||||
158<\/td>\n | 2.5\tInformation viewpoint 2.6\tService taxonomies 2.7\tEngineering viewpoint 2.8\tTechnology viewpoint <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | 3\tNormative references 4\tTerms and definitions and abbreviations 4.1\tTerms and definitions <\/td>\n<\/tr>\n | ||||||
161<\/td>\n | 4.2\tAbbreviations <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | 5\tNotation 5.1\tGeneral 5.2\tConformance class 5.3\tRequirements class <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | 5.4\tRules 5.5\tIdentifiers 5.6\tConceptual schemas 5.7\tDescriptions of concepts 5.8\tArchitecture patterns <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | 6\tOverview of geographic services architecture 6.1\tPurpose and justification 6.2\tRelationship to ISO\u00a019101-1 <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | 6.3\tInteroperability reference model based on ISO RM-ODP <\/td>\n<\/tr>\n | ||||||
167<\/td>\n | 6.4\tService abstraction <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | 6.5\tInteroperability <\/td>\n<\/tr>\n | ||||||
170<\/td>\n | 6.6\tUse of other geographic information standards in service specifications 7\tEnterprise viewpoint: A context for services 7.1\tEnterprise viewpoint <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | 7.2\tEnterprise viewpoint service specifications <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | 7.3\tExamples of relevant standards <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | 7.4\tExample and tools 8\tComputational viewpoint: A basis for service interfaces and chaining 8.1\tComponent and service interoperability and the computational viewpoint <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | 8.2\tServices, interfaces and operations <\/td>\n<\/tr>\n | ||||||
175<\/td>\n | 8.3\tComputational viewpoint service specifications 8.3.1\tRequirements class for computational viewpoint service specifications 8.3.2\tService interfaces with operations <\/td>\n<\/tr>\n | ||||||
177<\/td>\n | 8.3.3\tService behaviour and constraints <\/td>\n<\/tr>\n | ||||||
179<\/td>\n | 8.4\tService chaining 8.4.1\tGeneral <\/td>\n<\/tr>\n | ||||||
180<\/td>\n | 8.4.2\tAnatomy of a service chain <\/td>\n<\/tr>\n | ||||||
181<\/td>\n | 8.4.3\tService chain modelling <\/td>\n<\/tr>\n | ||||||
183<\/td>\n | 8.4.4\tServices organizer folder 8.4.5\tServices to enable service chaining <\/td>\n<\/tr>\n | ||||||
184<\/td>\n | 8.4.6\tArchitecture patterns for service chaining <\/td>\n<\/tr>\n | ||||||
189<\/td>\n | 8.4.7\tVariations on chaining patterns <\/td>\n<\/tr>\n | ||||||
190<\/td>\n | 8.5\tService metadata 8.6\tSimple service architecture <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | 8.7\tExamples of relevant standards 8.8\tExamples and tools: Service modelling with SoaML 9\tInformation viewpoint: A basis for semantic interoperability 9.1\tInformation model interoperability and the information viewpoint <\/td>\n<\/tr>\n | ||||||
192<\/td>\n | 9.2\tInformation viewpoint Service specifications <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | 10\tService taxonomies 10.1\tNeed for multiple service taxonomies <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | 10.2\tService taxonomies and requirements 10.3\tArchitectural reference model 10.4\tDefinition of the Architectural reference model 10.5\tUses of the Architectural reference model <\/td>\n<\/tr>\n | ||||||
197<\/td>\n | 10.6\tOverview of the Architectural reference model 10.6.1\tServices and service interfaces <\/td>\n<\/tr>\n | ||||||
198<\/td>\n | 10.6.2\tIdentifying services and service interfaces for geographic information 10.7\tTypes of geographic information services 10.7.1\tRequirement for service taxonomy 10.7.2\tTypes of information technology services relevant to geographic information <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | 10.7.3\tExtension of service types for geographic information 10.8\tGeographic architecture services taxonomy 10.8.1\tGeographic architecture services taxonomy requirements <\/td>\n<\/tr>\n | ||||||
201<\/td>\n | 10.8.2\tGeographic boundary\/human interaction services <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | 10.8.3\tGeographic model\/information management services <\/td>\n<\/tr>\n | ||||||
203<\/td>\n | 10.8.4\tGeographic workflow\/task management services 10.8.5\tGeographic processing services <\/td>\n<\/tr>\n | ||||||
206<\/td>\n | 10.8.6\tGeographic communication services 10.8.7\tGeographic system management and security services <\/td>\n<\/tr>\n | ||||||
207<\/td>\n | 10.9\tISO\u00a0suite of International Standards in geographic architecture services taxonomy 10.10\tGeographic service chaining validity <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | 10.11\tUser-perspective Lifecycle model for Services <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | 10.12\tUser-defined service taxonomies 10.13\tServices organizer folder (SOF) 10.13.1\tGrouping of services 10.13.2\tImage exploitation SOF <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | 10.13.3\tGeographic data fusion SOF <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | 10.14\tSemantic information models <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | 10.15\tExamples of relevant standards <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | 10.16\tExamples and tools 11\tEngineering viewpoint: A basis for distribution and communication patterns 11.1\tDistribution transparencies and the engineering viewpoint <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | 11.2\tDistributing components using a multi-tier architecture model <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | 11.3\tDistribution transparencies <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | 11.4\tEngineering viewpoint Service specifications <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | 11.5\tMulti-style SOA 11.6\tRelevant architectural styles 11.6.1\tService-oriented architectures <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | 11.6.2\tRepresentational State Transfer (REST) <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | 11.6.3\tWeb 2.0 <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | 12\tTechnology viewpoint: A basis for cross platform interoperability 12.1\tInfrastructure interoperability and the technology viewpoint <\/td>\n<\/tr>\n | ||||||
223<\/td>\n | 12.2\tNeed for multiple platform-specific specifications 12.3\tConformance between platform-neutral and platform-specific service specifications <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | 12.4\tFrom platform-neutral to platform-specific specifications 12.5\tTechnology objects 12.6\tTechnology viewpoint service specifications 12.6.1\tRequirements class for technology viewpoint <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | 12.6.2\tTechnology mappings <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | 12.7\tArchitectural classification according to cloud computing service categories <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | Annex\u00a0A (normative) Conformance <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | Annex\u00a0B (informative) Example user scenarios <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | Annex\u00a0C (informative) Principles for mapping to distributed computing platforms <\/td>\n<\/tr>\n | ||||||
248<\/td>\n | Annex\u00a0D (informative) Use case-based methodology <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | Annex\u00a0E (informative) Example \u2014 Use case template <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | Annex\u00a0F (informative) Service modelling \u2013 SoaML <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. Geographic information. Services<\/b><\/p>\n |