Geospatial User Feedback (GUF) is an OGC standard. Copyright (c) 2016 Open Geospatial Consortium. To obtain additional rights of use, visit http://www.opengeospatial.org/legal/. The feedback item is the container of the actual feedback. Every item is set into context by a combination of target citations and scopes. Identifier for the feedback item. It needs to be locally unique. Brief narrative description of this item, normally for display to a human Summary of the intentions with which the feedback was provided User's role in the context of this feedback item. A user may have several roles recorded in the GUF_UserInformation, but this is the one that apply for this feedback. The idea is for a single user to be able to embody more than one role, but only one in each item. Thus, a data producer employee may comment and normally speak freely as a end user, but e.g. issue a metadata override on behalf of the data provider if he explicitly chooses that role. He would only be allowed to choose roles from his user information, and maybe there could be additional restrictions. So users seeking reliable but "semi-official" metadata could look for overrides issued by the provider in that role. The date when the feedback item was created, updated etc. Identifiers of one or more items of feedback to which this item is a response. Populate only if the feedback item is responding to another feedback item (e.g. a comment about a previous comment). Maps to 1 or more themes or scientific domains within which the feedback was generated and is relevant. We identify EO domains using selected ontologies such as GEMET concepts. These are domain focus and unlike "tags", uses domain URNs defined in some ontology. <b>tag:</b> keyword-type additions to narrow down the context. The tag qualifier associates tags parts of a so-called folksonomy to the feedback item. Such free-form memes are often aggregated in "tag clouds", allowing a community to reach an informal understanding of these tags. The precision of such features is debateable, but in social networks they are often considered essential. language and character set used for documenting metadata Link to a item in an extenal repository that contains the feedback (not described inline). The Target unambiguously refers to pretext in the domain of discourse, such as a dataset, a sensor, a metadata document, etc. This should match a datasetURI or MD_Identifier for that resource. The parent is intended to model containment such as "this sensor is contained in this SOS". This is redundant, but avoids having to understand e.g. SensorML to uncover the relationship. Obviously, the parent should not have finer granularity than the child. Resource (could be the identifier of a dataset in a metadata catalog) to the geospatial target of the feedback. Actually, the feedback model does not depend on the target's type, it just postulates a canonicalized or otherwise "matchable" identifier in this field. This could take the form of an outside service to provide the necessary matching capability. resourceRef could be used to define the title of a group of targets (children) or to cite a target in a reporitory Resource (could be the identifier of a dataset in a metadata catalog) to the geospatial target of the feedback. Actually, the feedback model does not depend on the target's type, it just postulates a canonicalized or otherwise "matchable" identifier in this field. This could take the form of an outside service to provide the necessary matching capability. resourceRef could be used to define the title of a group of targets (children) or to cite a target in a reporitory Describes a type of resource the feedback is about; typically a dataset, a metadata record, a feature... or a subsets of a dataset or resource. Type of object the identifier points at, typically a dataset, a metadata record, a feature... A data centric focus describes sub-sets of a dataset or resource. It is to be interpreted as the intersection of the attributes which are specified, i.e. an unspecified attribute does not constrain the focus. A rating is intended to cover star-like low information content ratings. Unlike e.g. a report, it is aggregable by nature. To be restricted between 1 and 5 Inspired in https://software.ecmwf.int/wiki/display/CHAR/Significant+Events Focus on global climatic events. Do we change this to Keywords? The targets of an item describe its context, guided by one of the three possible roles primary, secondary and supplementary which define how a target is relevant to an item. Targets are intended to be comparable to each other, resulting in a comparison results such as "identical", "overlapping" or "disjoint", helping to establish an order of how relevant feedback is to a circumscribed issue. For supplementary information on the exact procedure carried out. The comment is the most generic feedback type. Depending on the foci, it may serve as answer, rating justification, or general comment. The user comment's body. Describes a user Contact details about the user and its organization. Application domains a user work in. User's expertise level in this particular context, will be restricted by a codelist The roles the user can play. User ID in an external system such as an ORCHID.