All pages with prefix

From Geostandards

All pages Display pages with prefix: Namespace: (Main) Talk User User talk Geostandards Geostandards talk File File talk MediaWiki MediaWiki talk Template Template talk Help Help talk Category Category talk

All pages | Next page (6.6.4 Metadata guidelines)

- activity diagram:	- class diagram	- object diagram
- sequence diagram and communication diagram	- state machine diagram	- use-case diagram:
1.1.1 Advantages of standards	1.1.2 Standards and interoperability	1.1.3 What are open standards?
1.1.4 What do standards result in?	1.1 What are geo-standards?	1.2.1 Overview and targeted group
1.2.2 ISO/TC211	1.2.3 The OGC	1.2 International standards
1.3.1 Overview and target group	1.3.2 CEN/TC 287	1.3.3 INSPIRE
1.3 European Standardisation	1.4.1 Overview and targeted group	1.4.2 NEN Standardisation
1.4.3 Geonovum	1.4.4 Electronic Government	1.4 Dutch Standardisation
1.5.1 ISO 19115 Metadata Standard	1.5.2 OGC Web Mapping Service WMS	1.5 Examples of ISO and OGC Standards
1.6.1 Framework of Geostandards	1.6 Framework of Geostandards	1.7.1 Achitecture
1.7 Architecture	1024 by 768 pixel resolution at 132 pixels per inch ppi No 40	10 It s market price 11
1 Framework Geo-standards	2.1.1 What is metadata?	2.1.2 Why metadata?
2.1.3 What can you do with it?	2.1.4 Where can you find metadata?	2.1.5 Applications
2.1.6 Discovery discovery	2.1 Introduction to Metadata	2.2.1 What is a standard for?
2.2.2 Standards for geo-information	2.2.3 Metadata standards	2.2.4 INSPIRE
2.2.5 Discovery standards	2.2 Metadata standards	2.3.1 How do you make metadata?
2.3.2 How do you make metadata from services?	2.3.3 Where in the working process?	2.3.4 Tips for gathering metadata
2.3.5 Publishing metadata	2.3.6 Harvesting	2.3.7 Validating
2.3.8 Discovery working process	2.3 Metadata in the working process	2.4.0 Overview of metadata elements
2.4.10 Subject	2.4.11 Keyword	2.4.12 Thesaurus
2.4.13 Thesaurus date	2.4.14 Thesaurus date type	2.4.15 Minimum x-coordinate
2.4.16 Maximum x-coordinate	2.4.17 Minimum y-coordinate	2.4.18 Maximum y-coordinate
2.4.19 Temporal cover	2.4.1 Title of the resource	2.4.20 Date of the resource
2.4.21 Date type of the resource	2.4.22 Grade of the description of quality	2.4.23 General description of origin
2.4.24 Scale of application	2.4.25 Resolution	2.4.26 Code Reference system
2.4.27 Responsible organisation for namespace reference system	2.4.28 Conformity indication with the specification	2.4.29 Clarification
2.4.2 Summary	2.4.30 Specification	2.4.31 Specification date
2.4.32 Specification date type	2.4.33 Legal restrictions to accessibility	2.4.34 Other constraints
2.4.35 Security restrictions	2.4.36 User constraints	2.4.37 Responsible organisation resource
2.4.38 Responsible organisation resource: email	2.4.39 Responsible organisation resource: role	2.4.3 Status
2.4.40 Metadata unique identifier	2.4.41 Parent unique identifier	2.4.42 Responsible organisation metadata
2.4.43 Responsible organisation metadata: role	2.4.44 Responsible organisation metadata: email	2.4.45 Metadata date
2.4.46 Language of the metadata	2.4.47 Metadata standard name	2.4.48 Metadata Standard version
2.4.49 Discovery metadata for data	2.4.4 Level of hierarchy	2.4.5 URL
2.4.6 Protocol	2.4.7 Name	2.4.8 Unique Identifier of the resource
2.4.9 Language of the resource	2.4 Metadata elements	2.5.0 Metadata elements for services overview
2.5.10 Service Type Version	2.5.11 Operation Name	2.5.12 DCP
2.5.13 Keyword value	2.5.14 Originating controlled vocabulary	2.5.15 Geographic location
2.5.16 Temporal Reference	2.5.17 Spatial resolution	2.5.18 Degree
2.5.19 Specification	2.5.1 Resource Title	2.5.20 Constraints
2.5.21 Conditions applying to access and use	2.5.22 Responsible party	2.5.23 Responsible party role
2.5.24 Metadata point of contact	2.5.25 Metadata language	2.5.26 Metadata date
2.5.27 The link to the metadata of the dataset and dataset series from the service	2.5.28 Discovery metadata for services	2.5.2 Resource abstract
2.5.3 Resource type	2.5.4 Resource locator	2.5.5 Connect Point Linkage
2.5.6 Coupled resource	2.5.7 Scoped Name	2.5.8 Coupling Type
2.5.9 Spatial data service type	2.5 Metadata elements for services	2.6.1 Bordering rectangle
2.6.2 Reference system	2.6.3 Geo shared licence	2.6.4 Optional set metadata of data
2.6.5 Multilingual metadata	2.6.6 Object and attribute information	2.6.7 Guidelines for sectors
2.6.8 Exchanging metadata	2.6 What you should also know	2 Metadata
3 SOA so what	4.1.1 Goal and scope of course	4.1.2 Pre-requisites: knowledge of OO-modeling, DBMS DDL/SQL and/or XML schema, specific domain/theme
4.1.3 Introduction of participants & teachers	4.1.4 Tools	4.1.5 Organization of course
4.1.6 Course reading material	4.1.7 Purpose IM: 1. enable communication, 2. built system	4.1.8 Inventory of participants' most favorite domains/themes
4.10.1 Convert model from hands-on 1 to SQL/DDL	4.10.2 Load the script into the DBMS	4.10.3 Insert data and perform some queries
4.10.4 Convert model to XML schema and inspect resulting XSD	4.10.5 Create XML data document from DBMS export to XML	4.10.6 Validate XML data against XML schema (optional)
4.10.7 Same steps as above but now for own model of hands-on 2 (with spatial data), manual corrections...	4.10 Hands-on 3: convert model	4.11.1 Summarize main points
4.11.2 Presentation of participants' hands-on result	4.11.3 Additional tips&tricks	4.11.4 National modeling activities (NEN3610+IMxx)
4.11.5 Discussion on model mapping	4.11.6 Further reading/studying	4.11.7 Evaluation by participants
4.11 Conclusion	4.1 Introduction	4.2.1 Basic principles
4.2.2 Advanced principles	4.2 UML Class diagram	4.3.1 Explanation of initial model assignment
4.3.2 Create UML class diagram for model with 3 or 4 classes	4.3.3 Define database tables for these objects (by hand)	4.3.4 Create XML schema for these objects (by hand?)
4.3.5 Evaluation of the results	4.3.6 Use of Enterprise Architect	4.3 Hands-on 1: basic tools
4.4.1 OGC/ISO/CEN/NEN	4.4.2 Focus on INSPIRE Generic Conceptual Model	4.4.3 GII context
4.4.4 Generic aspects: id's, references, time,etc	4.4.5.1 Topology (linear networks, partitions)	4.4.5.2 Observation data - resulting objects
4.4.5.3 Spatial object - relationship - person	4.4.5 Reusable model patterns:	4.4.6 Generic models, e.g. the 34 themes of INSPIRE
4.4 Frameworks	4.5.1 User requirements, use cases	4.5.2 Inventory of available related data sets
4.5.3 Analyze the differences (data components, checklists)	4.5.4.1 UML class diagram (with attributes, associations)	4.5.4.2 F&A catalogue with descriptions
4.5.4.3 Specific data types (enummerations, code lists and values)	4.5.4 Take initial decisions and develop model:	4.5.5 Cost-benefit analysis
4.5.6 Review with stakeholders (and revise if needed)	4.5.7 Test model, develop prototype data (and revise if needed)	4.5 Methodology
4.6.1 xx	4.6.2 Real world example from INSPIRE cadastral parcels	4.6.3 Link to ISO 19152 LADM
4.6.4 In total 8 Categories of use cases identified	4.6.5 Closer look at 2 use cases	4.6.6 Check list with summary of all use cases
4.6.7 Conflicts of interest, feasibility	4.6.8.1 Optional elements (objects, attributes, associations,...)	4.6.8.2 Advanced geometries (3D, non-linear,...)
4.6.8.3 Multi-scale/representations vs. vario-scale	4.6.8 Vision within a model (growing options)	4.6 Example Information Model
4.7.1 Identify and create two use case descriptions	4.7.2 Go over the data components and describe needs	4.7.3 Explore information content
4.7.4 Analyze differences between needs and availables	4.7.5 Develop UML class diagram for your UML model	4.7 Hands-on 2: own model
4.8.1 OMG MDA principles PIM, PSM	4.8.2 Generate implementations	4.8.3.1 - PSM1 (PostgreSQL/PostGIS) - SQL/DDL
4.8.3.2 - PSM2 (XML/GML schema) - XSD	4.8.3.3 - PSM3...	4.8.3 Generic PIM - Specific PIM
4.8.4 Run SQL/DDL within DBMS to set up model, load/create data	4.8.5 Generate XML/GML according to XSD	4.8 Implement the model
4.9.1 Add business rule, i.e. constraints on the data within the model	4.9.2 Classification main categories of constraint types	4.9.3 Describe in natural text using the literal entities from UML class diagrams (classes, attributes, associations)
4.9.4 Formalize the constraints into OCL (object constraint language)	4.9.5 Implementation/use of constraints ? non trivial	4.9.6.1 DBMS: either constraints views selection violations or triggers and procedures (heavy transform)
4.9.6.2 XML/XSD: literal encoding of OCL string	4.9 Adding more semantics	4 Information modeling
4months and two weeks no cigarette saving a lot 22	5.1 Scope of the course	5.2.1 Sensor Networks
5.2.2 What is Sensor Web Enablement?	5.2.3 Overview of the SWE Architecture	5.2.4 Benefits of SWE
5.2 Introduction to SWE	5.3.1 SWE common	5.3.2 O&M
5.3.3 SensorML	5.3 SWE Information Model	5.4.1 Sensor Observation Service
5.4.2 Sensor Planning Service	5.4.3 Sensor Alert Service	5.4.4 Sensor Discovery
5.4 SWE Services Model	5.5.1 Application of SWE in environmental monitoring and disaster management	5.5.2 Applying SWE in the hydrological domain
5.5.3 Further projects	5.5 Overview of projects applying SWE	5.6 Literature
5 Sensor Web Enablement	6.1.1 Spatial Data Infrastructures	6.1.2 Requirements for a European SDI
6.1.3 Existing foundation for a European SDI	6.1 Background and Motivation	6.2.1 Background and history
6.2.2 The five components of the Directive	6.2.3 Implementation, status and schedule	6.2.4 Groups and responsibilities within INSPIRE
6.2.5 European initiatives and projects in the context of INSPIRE	6.2.5 INSPIRE Implementing Rules and INSPIRE Guidance Documents	6.2.6 European and Global initiatives in the context of INSPIRE
6.2.6 INSPIRE and global initiatives like GEOSS and GMES	6.2 Overview and Context	6.3.1 Relationship between the different components, in particular spatial data, metadata, registers, and network services
6.3.2 Terminology	6.3 Technical Architecture Overview	6.4.10 Coordinate referencing
6.4.11 Multi-lingual text and cultural adaptability	6.4.12 Data quality	6.4.13 Metadata for evaluation and use
6.4.14 Multiple representations	6.4.15 Consistency between data	6.4.16 Portrayal model
6.4.17 Conformance	6.4.18 Generic Network Model	6.4.19 Gazetteers
6.4.1 Requirements of the INSPIRE Directive	6.4.20 Encoding and data formats	6.4.21.1 glossary
6.4.21.2 feature concept dictionary	6.4.21.3 code lists	6.4.21.4 UML model
6.4.21.4 future registers	6.4.21 INSPIRE registers	6.4.22.1 Coordinate reference systems
6.4.22.2 Geographical grid systems	6.4.22.3 Geographical names	6.4.22.4 Administrative units
6.4.22.5 Addresses	6.4.22.6 Cadastral parcels	6.4.22.7 Transport networks
6.4.22.8 Hydrography	6.4.22.9 Protected sites	6.4.22 Annex I data specifications
6.4.23 Outlook to Annex II/III data specifications	6.4.24 Extensions by countries or communities	6.4.2 Interoperability of spatial data
6.4.3 INSPIRE data scope	6.4.4 Modelling Framework	6.4.5 Generic Conceptual Model
6.4.6 ISO 19100 series of International Standards	6.4.7 Rules for application schemas and feature catalogues	6.4.8 Identifier Management
6.4.9 Object referencing modelling	6.4 Interoperabilty of spatial data sets / INSPIRE data specifications	6.5.1 Network Service Architecture
6.5.2 The INSPIRE SOAP/WSDL framework	6.5.2 View Services	6.5.3 Discovery Services
6.5.3 Discovery Services old	6.5.3 Rights management and access control	6.5.4 Download Services
6.5.4 e-Licensing and e-Commerce	6.5.5 Transformation Services	6.5.5 View Services
6.5.6 Discovery Services	6.5.6 Invoke spatial data service services	6.5.7.1 Direct access
6.5.7.2 Pre-defined dataset download	6.5.7 Download Services	6.5.8.1 General structure
6.5.8.2 Coordinate transformations	6.5.8.3 Transformations between schemas	6.5.8 Transformation Services
6.5.9.1 Performance and Quality of Service requirements	6.5.9.2 Relationship with OGC and ISO standards	6.5.9 Invoke spatial data service services
6.5 Network Services	6.6.1 Requirements of the INSPIRE Directive	6.6.2 INSPIRE Metadata scope
6.6.3 INSPIRE Metadata elements	6.6.4.1 Implementation according to ISO 19000 series	6.6.4.2 Implementation according to Dublin Core