I would like to second Jim's statement. It is important to implement a common language, including terms and definitions in our working group. This is something we need to work on and I do not
see a degree of urgency here.
Regarding the DSSC, I can only agree. The DSSC work does not even consider the Dataspace Protocol as relevant, which is a pity. It does not recognize the Eclipse Dataspace Working Group as
relevant for its work.
Finally, even while the regulations use data space/Data Space, the groups in CEN/CENELEC use the word dataspace(s).
I doubt that we will solve the issue with the term Data Space/dataspace here, but we can be consistent here in the Eclipse __Dataspace__ Working Group.
Cheers
Sebastian
From: dataspace-wg-spec <dataspace-wg-spec-bounces@xxxxxxxxxxx>
On Behalf Of Jim Marino via dataspace-wg-spec
Sent: Tuesday, July 16, 2024 7:46 AM
To: Dataspace WG Spec discussions <dataspace-wg-spec@xxxxxxxxxxx>
Cc: Jim Marino <jim.marino@xxxxxxxxx>; Eclipse Management Office EMO <emo@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [dataspace-wg-spec] [BALLOT] Approval to Create the Eclipse Data Rights Policies and Profiles (DRP) Specification Project
Dataspace is a defined term in the DSP specification and other specifications which build on it should refer explicitly to the correct form. It may not change the meaning if you assume the intent was to use the defined term. However, it
could be interpreted as meaning something broader than the term. This may be less important in a scope statement, but specification text should correctly use the term.
Citing the “Data Spaces Support Center” has come up in the past. We should be clear that the DSP and base specification work here is in no way tied to or based on text or concepts it produces. In other words, there are no normative linkages
to the work that the center creates.
Does changing from "data spaces" to "dataspaces" change the meaning of the scope in any meaningful way?
I assume that the answer is no. Please advise if otherwise.
We agreed early on that EDWG will spell it Dataspace to show that it is a special technical term and to make it easier to be discoverable via search engines.
Therefore all protocols and implementation projects so far spell it without the space.
Hi,
the Glossary of the Data Spaces Support Centre and the data acts of the European Commission use: data space or Data Space.
Ulrich Ahle
| Chief Executive Officer
Gaia-X European Association for Data and Cloud AISBL
ulrich.ahle@xxxxxxxxx
| www.gaia-x.eu |
Avenue des Arts 6-9
1210 Bruxelles/Brussels
Belgium
News & Press
|
Events | Media|
Membership | www.gaia-x.eu
PRIVACY AND CONFIDENTIALITY NOTICE: For details about what personal information we collect and why, please see our Privacy Policy on our website at
http://www.gaia-x.eu/privacy-policy.
This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and/or legally privileged information.
Any unauthorized use or disclosure, copying and/or distribution of the content of this e-mail message and attachments is prohibited. If you are not the intended recipient, please contact us by reply e-mail and destroy all copies of the original message and
attachments immediately. Thank you.
Please consider the environment before printing this e-mail. Save about 200ml water, 2g CO2, 0.05kWh power, and 2g wood.
In the DRP scope below shouldn’t we replace “data spaces” with “dataspaces” for consistency?
: : Best
regards, Eric Samson
Standards & Technology Diplomat
Corporate Standards Group
Microsoft Privacy, Safety & Regulatory Affairs
+1 iSHARE
Warm Regards,
iSHARE.eu : The non-profit federated trust framework for data spaces
Dear Specification Committee,
My apologies for the earlier false start. We're restarting this ballot with understanding that the steering committee has given their approval to proceed.
Your vote is required to approve the creation of the Eclipse Data Rights Policies and Profiles (DRP) Specification Project with the following scope:
The Eclipse Data Rights policies profile provides a set of specifications designed to facilitate interoperable trust between entities that comply with Trust Frameworks and data spaces requirements. These specifications define the schemas
required for entities to identify and authenticate each other to share/access data based on the authorisations given by the data rights holder.
The project proposal can be found here: https://projects.eclipse.org/proposals/eclipse-data-rights-policies-and-profiles-drp
Per the Eclipse Foundation Specification Process, this will be a seven day ballot, ending on
Thursday July 18 2024 that requires a super-majority positive vote of the Dataspace Working Group specification committee members (note that there is no veto). Community input is welcome, but only votes cast by specification committee representatives
will be counted.
Specification committee representatives, your vote is hereby requested. Please respond with +1 (positive), +0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated.
--
The Eclipse Management Organization |
Eclipse Foundation
![]()
_______________________________________________
dataspace-wg-spec mailing list
dataspace-wg-spec@xxxxxxxxxxx
To unsubscribe from this list, visit
https://accounts.eclipse.org
_______________________________________________
dataspace-wg-spec mailing list
dataspace-wg-spec@xxxxxxxxxxx
To unsubscribe from this list, visit
https://accounts.eclipse.org
--
Wayne Beaton
Director of Open Source Projects |
Eclipse Foundation
My working day may not be your working day! Please don’t feel obliged to read or reply to this e-mail outside of your normal working hours.
|
