Use Case: link information resources (methodologies) and business processes

[ChLaaboudi]

For the future extension of the data model, I would like to contribute with a practical requirement we have in Eurostat. We maintain a list of statistical methodologies (catalogue of ESS standards) that we recently transformed in RDF.

1) A number of methodologies reference GSBPM phase(s) . In that purpose, we reused <coos:enables> to link a methodology with its relevant GSBPM phases.

2) Each resource is defined by the rdf:type skos:Concept and dct:Standard. If we follow GSIM, a methodology can be considered as an Information Resource. Couldn't we include it as a new class (InformationResource) of coos?

You'll find here an RDF description of an ESS methodology: ess_standard.txt

[InKyungChoi]

Regarding 2 - GSIM revision team is currently trying to add a new GSIM class that could be used for documents such as methodological handbook, policies and standards. I think this new class suits better than Information Resource. You can find the on-going discussion here. I will make cross-refernece in GSIM github too.

[FlavioRizzolo]

A number of methodologies reference GSBPM phase(s) . In that purpose, we reused to link a methodology with its relevant GSBPM phases.

How about creating a new property called <coos:informs>? That would be stronger than "seeAlso", but weaker than "enables", which seems to place it in the right spot.

[ChLaaboudi]

Dear @JALinnerud,

We published the dataset of ESS_Standards in ShowVoc: https://showvoc.op.europa.eu/#/datasets/ESTAT-ESS_STANDARDS/data.

Please be aware it is not the final version.

Best regards,

Christine

[FlavioRizzolo]

Following this recent GSIM development:

Regarding 2 - GSIM revision team is currently trying to add a new GSIM class that could be used for documents such as methodological handbook, policies and standards. I think this new class suits better than Information Resource. You can find the on-going discussion here. I will make cross-refernece in GSIM github too.

We should probably update COOS as follows.

In GSIM, we decided to name that class "Reference Documents" (definition and explanatory text can be found in the GSIM issue liked above). A coos:ReferenceDocuments class should be added to COOS as well to reflect that addition to GSIM and part of the "raison d'être" of this issue.

The second part is what to link to coos:ReferenceDocuments, and how. The first obvious candidates are coos:SubProcess and coos:Task, but it could be directly linked to coos:Activity so that it can be used at any level of granularity.

I suggested to add a coos:informs property to stablish the link. I'm also thinking we could make the property activity-centric and name it coos:isInformedBy, but that might get confused with prov:wasInformedBy, although the range of the latter is prov:Activity instead of coos:InformationObject.

[FlavioRizzolo]

Link to the GSIM revision issue (#3)

Proposed definition of coos:ReferenceDocuments, in line with GSIM: "Documents that are used to support, inform and guide the business processes"

[FranckCo]

A first version of the ReferenceDocument class is provided in commit c9ded05695d5efc30b989ef27581cde25a72c369. Note the following:

• The singular is used instead of the proposed ReferenceDocuments. Each document is a specific resource, so it is preferable to link the documents individually.
• coos:ReferenceDocument is defined as a subclass of foaf:Document
• the Spanish translations are missing

[FranckCo]

A first version of the informs property is provided in commit 1a49994d393d4116b76bdf312dbcaaeb2b509439. Note the following:

• The domain of the property is coos:ReferenceDocument and its range is coos:Activity
• Multiple occurrences of the property can be used to link multiple instances of coos:ReferenceDocument (see above)
• The Spanish translations are missing

[FranckCo]

Decided at 9/26 meeting: @zoltanvereczkei to provide an example using ReferenceDocument and informs.

[zoltanvereczkei]

An example:

Statistical organisations regularly produce seasonally adjusted GDP time series data. For the creation of these statistical datasets, the unadjusted (raw) time series data and methodological guidelines and tools supporting seasonal adjustment are used. The end product is a seasonally and calendar (effects) adjusted and reconciled GDP time series data.

An example for the use of Handbook on Seasonal Adjustment as a coos:ReferenceDocument for this statistical activity is as follows: