oslc-core message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: OSLC C'ombined Core and Domains TC meeting minutes 20190516
- From: "Jim Amsden" <jamsden@us.ibm.com>
- To: "OASIS OSLC Core TC Discussion List" <oslc-core@lists.oasis-open.org>, oslc-domains@lists.oasis-open.org
- Date: Thu, 16 May 2019 11:15:44 -0400
Jim Amsden (IBM):Previous Minutes: https://lists.oasis-open.org/archives/oslc-domains/201905/msg00006.html
Nick Crossley
(IBM): Nick will scribe
Nick Crossley
(IBM): Andrew sent his regrets
Nick Crossley
(IBM): List of attendees:
David Honey (Persistent/IBM), Jad (kth), Jad (kth)1, Jim Amsden (IBM),
Nick Crossley (IBM)
Jim Amsden
(IBM): Open Project
* Announcement May 8 but points to
the old OSLC organization...
* Move oslc-core
ReSpec updates for Open Project
TRS Draft for TC review
Config Management
Query
QM
Nick Crossley
(IBM): Move to Open Project
- ballots approved,
Nick Crossley
(IBM): CLAs signed
Nick Crossley
(IBM): announcements made
Nick Crossley
(IBM): reorganized GitHub
content
Jim Amsden
(IBM): https://github.com/oasis-tcs/oslc-core
Nick Crossley
(IBM): Nick: change from specs
to docs top level folder was slightly specious
Nick Crossley
(IBM): Discussion of new structure
- URIs had to change to handle merge with domains, symmetry demanded change
to core spec location
Nick Crossley
(IBM): Styles will change
- need to move respect to new GitHub location with those new stlyes
Nick Crossley
(IBM): Repo has not yet been
renamed/reassigned to new open project organization - so repo URIs will
change once more.
Nick Crossley
(IBM): Jim will try to get
that reassignment done.
Nick Crossley
(IBM): Action: Jim Amsden
to move the GitHub repo to new org.
Nick Crossley
(IBM): Or request Chet to
do so.
Nick Crossley
(IBM): What to use for the
group calendar? Jim suggests Google Calendar, perhaps next week.
Nick Crossley
(IBM): Note that old TCs remain
open for 30 days.
Jim Amsden
(IBM): 1. Get the templates
updated to OSLC OP content
2. Make the ReSpec updates required
to render the specs with the new OP format
3. Vote to submit QM spec for public
review and create the first Project Specification revision 01 (instead
of committee specification) as a test to ring out the OP processes.
4. Republish all existing Domains
committee specifications
5. Address review comments and create
a revision of the Query spec as a Project Specification 02
6. Create a new revision of the Core
specifications and submit to public review (to handle changes for conformance
sections, and URL link updates)
7. Then focus on TRS and Configuration
Management.
Nick Crossley
(IBM): Move to new repo location
must be done before these changes (including new Respec repo).
Nick Crossley
(IBM): Jim recalls there was
a spreadsheet or similar note on Query spec feedback
Nick Crossley
(IBM): We will investigate
if the new publishing process can avoid the need to change URIs in links
(use of relative links).
Nick Crossley
(IBM): Nick: can we also publish
rough committee drafts for TRS and Config Management before they have the
right formats for full specifications?
Nick Crossley
(IBM): Github repos no longer
suitable for casual viewing, so we need to find other ways to allow public
viewing of not-yet-published specs.
Nick Crossley
(IBM): We can publish rough
drafts and other notes on open-services.net, avoiding any need for OASIS
involvement, or we could ask for some material to be published at OASIS
docs.
Nick Crossley
(IBM): Developers can use
local file access, which requires changing the permissions on your browser,
or using a local web server as suggested by Andrew in the mailing list.
Nick Crossley
(IBM): Nick: no progress yet
on Respec.
Nick Crossley
(IBM): Nick: have started
to look at TRS issues - there is no TRS vocabulary subdirectory in the
core folder on hugo - what is the process for getting the vocabs, etc.,
to hugo?
Nick Crossley
(IBM): Look at https://jazz.net/ns/
Nick Crossley
(IBM): Nick: I think we should
follow that jazz.net example, with appropriate redirects for the multiple
different formats.
Nick Crossley
(IBM): Need to discuss the
publishing process with Andrew.
Nick Crossley
(IBM): Start with vocabs,
then add shapes.
Nick Crossley
(IBM): Nick will have an updated
ReSpec in new repo by next meeting.
Jim Amsden
(IBM): 1. Get the templates
updated to OSLC OP content
2. Make the ReSpec updates required
to render the specs with the new OP format
3. Vote to submit QM spec for public
review and create the first Project Specification revision 01 (instead
of committee specification) as a test to ring out the OP processes.
4. Republish all existing Domains
committee specifications
5. Address review comments and create
a revision of the Query spec as a Project Specification 02
6. Create a new revision of the Core
specifications and submit to public review (to handle changes for conformance
sections, and URL link updates)
7. Then focus on TRS and Configuration
Management.
8. Determine a process for publishing
open project specifications
1. Publish rendered
specifications to OASIS
2. Publish updated
vocabularies to open-services.net
3. Publish a version
of the resource shapes to open-services.net
Nick Crossley
(IBM): Nick: #8 needs to be
done earlier.
Nick Crossley
(IBM): Jim will create issues
for the above list of steps/actions.
List of attendees:
David Honey (Persistent/IBM), Jad (kth), Jim Amsden (IBM), Nick Crossley
(IBM)
--
Jim Amsden, Senior
Technical Staff Member
ELM Quality Manager
919-525-6575
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]