2001
DOI: 10.1045/june2001-hill
|View full text |Cite
|
Sign up to set email alerts
|

A Content Standard for Computational Models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2001
2001
2024
2024

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 19 publications
(7 citation statements)
references
References 0 publications
0
7
0
Order By: Relevance
“…Well-known geoprocessing functions stem from well-known concepts (Hill et al, 2001). Normative specifications such as OGC (1999) implicitly use concepts when they define the generic behavior of an operation.…”
Section: Conceptsmentioning
confidence: 99%
See 1 more Smart Citation
“…Well-known geoprocessing functions stem from well-known concepts (Hill et al, 2001). Normative specifications such as OGC (1999) implicitly use concepts when they define the generic behavior of an operation.…”
Section: Conceptsmentioning
confidence: 99%
“…Hill et al (2001) propose that symbolic (i.e. mathematical or logical) representations precede algorithmic representations of computing models which are then turned into programmatic implementations.…”
Section: Generic Profiles For Functions and Algorithmsmentioning
confidence: 99%
“…Some studies have begun to address the problem of designing a metadata framework for computational models. The Content Standard for Computational Models (Hill et al, 2001) was one of the first attempts at providing detailed metadata about a numerical model that includes the input and output data for model scenarios. Wosniok and Lehfeldt (2013) provide a concept for metadata-driven architecture for computational fluid dynamics simulations and a way to 5 integrate model descriptions into spatial data infrastructures.…”
Section: Introductionmentioning
confidence: 99%
“…It also may be necessary to store the same version of the needed software with the data (Lynch, 2008). Recommendations for the management of models and modeling data also advocate storing the software with the data (Hill, Crosier, Smith, & Goodchild, 2001;Cavalcanti, Mattoso, Campos, Llirbat, & Simon, 2002;Hunter, 2006). Such solutions can help to mitigate the risks to data that are associated with software dependencies if the software can be reused and if any other dependencies that are required by the software also are addressed.…”
Section: Introductionmentioning
confidence: 99%