Skip to main content
European Commission logo
Joinup logo
  • Interoperable Europe
  • Interoperability Solutions
  • Sign in
  • Create an account

    As a signed-in user you can create content, become a member of a community, receive notifications on your favourite solutions and topics, and access all other features available on the platform.

    • Home
    • Interoperable Europe
    • Interoperability Solutions
    • Sign in
    • About us
Member for: 8 years

Ana Fernández de Soria Risco

Comments to the final draft of CPSV-AP v2.1

Description This issue was shared by Nicola Guarino via the mailing list: 1. Definition of public service and service identifier I raised this issue in the past, but it was never discussed in the WG…

1
discussion

Public service categories

Description This issue was raised by Alexandros Gerontas during the final CPSV-AP v2.0 revision webinar. He asked to include categories to classify public services, in addition to the events…

0
discussion

Service user and provider properties

Description This issue was raised by Nicola Guarino during the final CPSV-AP v2.0 revision webinar. He asked to include the service user to the specifications, and change the cardinality of the…

0
discussion

Addition of properties to Contact Point class

Description This issue was raised by Alexandros Gerontas through the mailing list: I think the following properties might be added to the Contact Point class: Name, address, fax Proposed solution The…

0
discussion

Cardinality of the Has Contact Point property

Description This comment was made by Alexandros Gerontas through the mailing list: I think the cardinality of the property Has Contact Point should be 0..n. For example, a public service (PS)…

0
discussion

Errors on the second draft of the CPSV-AP

Description The following errors were raised by Dieter De Paeper through the mailing list: I see some confusion regarding the identifier attribute. From a previous joinup issue, I understood…

0
discussion

Specialise the Related Service and Spatial properties

Description This issue was raised by Dieter De Paepe through the mailing list: The Related Service property is mapped to dct:relation, which has a pretty vague definition: "A related resource...". As…

2
discussion

Relate the Criterion Requirement and Evidence

Description This issue was raised by Karolina Wolniewicz through the mailing list: The Criterion Requirement is not related directly to the Evidences. In our opinion, they should be linked. Example…

1
discussion

CPSV-AP v2.0 Revision WG Virtual Meeting - Webinar 3

27/09/2017 event

Type of Formal Framework

Description This comment was shared by Ignacio Serrano through the mailing list: In my opinion, the controlled vocabulary of property "Type (dct:type)" should not be limited to the Resource Types…

5
discussion

Criterion Requirement class - Cardinality of Type property

Description This issue was raised by Ignacio Serrano through the CPSV-AP mailing list: Why is property "Type (dct:type)" mandatory ([1..1]) only in this class? This property is not mandatory in other…

1
discussion

Comments on the example included on CPSV-AP v2.0

Description These comments were shared by Ignacio Serrano through the mailing list: 1) Maybe I am wrong, but I think that skos:prefLabel should be "The Finnish Patent and Registration Office", and not…

1
discussion

Pagination

  • Current page 1
  • Page 2
  • Page 3
  • Page 4
  • Page 5
  • Page 6
  • Page 7
  • Next page
  • Last page

Joinup

v1.90.4

About us

  • What is Joinup
  • Joinup Licensing Assistant
  • EIF Online Assistant
  • EIF Toolbox
  • Interoperable Europe

Help and support

  • Take a tour
  • Frequently Asked Questions (FAQ)
  • Contact Joinup Support
  • How-to & video tutorials
  • Satisfaction survey
  • Federation of solutions
  • Legal notice
  • Privacy statement

European Commission

  • About the Commission's new web presence
  • Resources for partners
  • Cookies
  • Contact European Commission
  • Europa Analytics

Follow us

  • Newsletter subscription
  • Newsletter archive
  • Twitter
  • LinkedIn