|
Re: Suspect links
I was trying to distinguish the content hash from state. If you create a new version of a versioned artifact and change none of its data, that will create a new state, and that state will be
I was trying to distinguish the content hash from state. If you create a new version of a versioned artifact and change none of its data, that will create a new state, and that state will be
|
By
David Honey2
·
#1030
·
|
|
Re: Suspect links
David
It does represents a state within the resource, not necessarily the total state represented by its memory footprint. This is similar to where we use explicit state models of objects, that
David
It does represents a state within the resource, not necessarily the total state represented by its memory footprint. This is similar to where we use explicit state models of objects, that
|
By
"Eran Gery"
·
#1029
·
|
|
Re: Suspect links
Sounds like the content hash fullfills the same functionality as the ETag?
No, they serve different purposes and have different usage. An Etag header value directly represents the state of a
Sounds like the content hash fullfills the same functionality as the ETag?
No, they serve different purposes and have different usage. An Etag header value directly represents the state of a
|
By
David Honey2
·
#1028
·
|
|
Re: Suspect links
Thanks Eran and David for your help
Sounds like the content hash fullfills the same functionality as the ETag?
From your link
Thanks Eran and David for your help
Sounds like the content hash fullfills the same functionality as the ETag?
From your link
|
By
Jad El-Khoury
·
#1027
·
|
|
Re: Suspect links
The point about using a content hash is that it is not necessarily state-specific. For example, a user might change a custom property on a requirement, and because that is not used for the content
The point about using a content hash is that it is not necessarily state-specific. For example, a user might change a custom property on a requirement, and because that is not used for the content
|
By
David Honey2
·
#1026
·
|
|
Re: Suspect links
Worth adding that the hash represents a state of a resource, as validity is across particular resource states.
A specific way to encode a state is considering a version of a resource. That means that
Worth adding that the hash represents a state of a resource, as validity is across particular resource states.
A specific way to encode a state is considering a version of a resource. That means that
|
By
"Eran Gery"
·
#1025
·
|
|
Re: Suspect links
Jad,
I sounds like you’re describinglink validity. See https://www.ibm.com/docs/en/elm/7.0.1?topic=traceability-link-validity
There is a published vocabulary for it
Jad,
I sounds like you’re describinglink validity. See https://www.ibm.com/docs/en/elm/7.0.1?topic=traceability-link-validity
There is a published vocabulary for it
|
By
David Honey2
·
#1024
·
|
|
Re: Suspect links
Jad
Suspect links related to any oslc link. not specific to “parent/child”. A classical use case is a link between a requirement and a design element that refines it.
Also, Suspect information
Jad
Suspect links related to any oslc link. not specific to “parent/child”. A classical use case is a link between a requirement and a design element that refines it.
Also, Suspect information
|
By
"Eran Gery"
·
#1023
·
|
|
Suspect links
Hi
When creating links between applications, is there some OSLC mechanism to identify and tag “Suspect” OSC links? If not covered by OSLC, any good hints on some good practices?
For
Hi
When creating links between applications, is there some OSLC mechanism to identify and tag “Suspect” OSC links? If not covered by OSLC, any good hints on some good practices?
For
|
By
Jad El-Khoury
·
#1022
·
|
|
OSLC-OP Meeting Minutes 20221027
https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/20221027.md
https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/20221027.md
|
By
Jim Amsden
·
#1021
·
|
|
Now: oslc-op Weekly Contributors Meeting - 10/27/2022
#cal-notice
oslc-op Weekly Contributors Meeting
When:
10/27/2022
10:00am to 11:00am
(UTC-04:00) America/New York
Where:
https://meet.jit.si/oslc-op
Organizer: Jim Amsden jamsden@...
View
oslc-op Weekly Contributors Meeting
When:
10/27/2022
10:00am to 11:00am
(UTC-04:00) America/New York
Where:
https://meet.jit.si/oslc-op
Organizer: Jim Amsden jamsden@...
View
|
By
Group Notification <noreply@...>
·
#1020
·
|
|
OSLCFest 2022 - Call for Presentations
The OSLCFest is the best place to learn first hand about OSLC solutions, as well as related open-source projects and standards. The 4th OSLCfest 2022 will take place virtually on November 15-17, with
The OSLCFest is the best place to learn first hand about OSLC solutions, as well as related open-source projects and standards. The 4th OSLCfest 2022 will take place virtually on November 15-17, with
|
By
Axel Reichwein
·
#1019
·
|
|
Formal notice of intent to publish OSLC Tracked Resource Set version 3.0 Project Specification Revision 02
The rules require us to notify you at least 14 days before submitting the ballots for the spec drafts publication. We are hereby notifying you of the OSLC-OP intention to publish OSLC Tracked Resource
The rules require us to notify you at least 14 days before submitting the ballots for the spec drafts publication. We are hereby notifying you of the OSLC-OP intention to publish OSLC Tracked Resource
|
By
Jim Amsden
·
#1018
·
|
|
OSLC-OP Meeting minutes for 2022-10-20
https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-10-20.md
https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-10-20.md
|
By
Jim Amsden
·
#1017
·
|
|
OSLC-OP Meeting minutes for 2022-10-20
https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-19-20.md
https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-19-20.md
|
By
Jim Amsden
·
#1016
·
|
|
Now: oslc-op Weekly Contributors Meeting - 10/20/2022
#cal-notice
oslc-op Weekly Contributors Meeting
When:
10/20/2022
10:00am to 11:00am
(UTC-04:00) America/New York
Where:
https://meet.jit.si/oslc-op
Organizer: Jim Amsden jamsden@...
View
oslc-op Weekly Contributors Meeting
When:
10/20/2022
10:00am to 11:00am
(UTC-04:00) America/New York
Where:
https://meet.jit.si/oslc-op
Organizer: Jim Amsden jamsden@...
View
|
By
Group Notification <noreply@...>
·
#1015
·
|
|
FW: [OSLC forum] [OSLC Open Project] Steps to contribute to the Automation Domain
Hi
It would be interesting to hear about their results. Can we suggest one of our regular Thursday meetings? Or should we organize another timeslot (where those interested can join?)
Similar
Hi
It would be interesting to hear about their results. Can we suggest one of our regular Thursday meetings? Or should we organize another timeslot (where those interested can join?)
Similar
|
By
Jad El-Khoury
·
#1014
·
|
|
OSLC-OP 2022-10-13 Meeting Minutes
See https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-10-13.md
See https://github.com/oslc-op/oasis-open-project/blob/master/minutes/2022/2022-10-13.md
|
By
Jim Amsden
·
#1013
·
|
|
Now: oslc-op Weekly Contributors Meeting - 10/13/2022
#cal-notice
oslc-op Weekly Contributors Meeting
When:
10/13/2022
10:00am to 11:00am
(UTC-04:00) America/New York
Where:
https://meet.jit.si/oslc-op
Organizer: Jim Amsden jamsden@...
View
oslc-op Weekly Contributors Meeting
When:
10/13/2022
10:00am to 11:00am
(UTC-04:00) America/New York
Where:
https://meet.jit.si/oslc-op
Organizer: Jim Amsden jamsden@...
View
|
By
Group Notification <noreply@...>
·
#1012
·
|
|
OSLC for Products - next discussion
Continue the discussion:
PTC’s approach to ALM-PLM integration using OSLC
Feedback and follow on discussion
Potential path ahead – discussion on goals and objective of a potential
Continue the discussion:
PTC’s approach to ALM-PLM integration using OSLC
Feedback and follow on discussion
Potential path ahead – discussion on goals and objective of a potential
|
By
G Bachelor <outlook_E832D20E4338AAC8@...>
·
#1011
·
|