Hi Chet, Thank you for information. Now I understand. Arthur, Do you think we have to make current draft consistent to current URL( I mean at SVN address) ? Best regards, Kaz From: oslc-promcode@lists.oasis-open.org [mailto:oslc-promcode@lists.oasis-open.org] On Behalf Of Chet Ensign
Sent: Tuesday, December 02, 2014 1:37 AM
To: Funakoshi Kazuhiro(船越 和大)
Cc: Arthur Ryman; oslc-promcode@lists.oasis-open.org
Subject: Re: [oslc-promcode] Re: Including files in specifications for PROMCODE Hi Kaz, docs.oasis-open.org/oslc-promcode/... is where your approved TC work products will be loaded and managed once the TC begins approving Committee Specification Drafts, public reviews and the like. The working drafts you produce prior to that step belong in your document repository or in the SVN. On Thu, Nov 27, 2014 at 1:17 AM, Kazuhiro Funakoshi <k-f@bk.jp.nec.com> wrote: Arthur,
OK, I did it.
I agree with you. Cleaner URLs are needed. Thank you in advance for stable
URL information.
I use the repository is not for publishing but for version control among our
TC members. Using wiki cannot manage versions with multiple wiki pages. So
basically, I will also publish at wiki at some milestones of drafts. We can
choose using document repository(doc.oasis-open.org) or wiki for publish, or
whatever OASIS recommends.
--
Kaz
-----Original Message-----
From: oslc-promcode@lists.oasis-open.org
[mailto:oslc-promcode@lists.oasis-open.org] On Behalf Of Arthur Ryman
Sent: Thursday, November 27, 2014 4:10 AM
To: Chet Ensign; oslc-promcode@lists.oasis-open.org
Cc: Steve K Speicher
Subject: [oslc-promcode] Re: Including files in specifications for PROMCODE
Chet - Thx.
Kaz - Please also upload the generated Turtle files to SVN. I only see the
generated HTML. This gives us stable URLs, e.g.
for HTML:
https://tools.oasis-open.org/version-control/browse/wsvn/oslc-promcode/shape
/trunk/Project.html
for Turtle:
https://tools.oasis-open.org/version-control/browse/wsvn/oslc-promcode/shape
/trunk/Project.ttl
However, we should really define cleaner URLs and set up HTTP redirects from
those to the SVN URLs. The redirects should also handle content negotiation.
We did this on the OSLC website for RDF vocabulary documents.
Steve pointed out that OASIS did have a mechanism for assigning cleaner
URLs. I will follow up on that.
_________________________________________________________
Arthur Ryman
Chief Data Officer
SWG | Rational
905.413.3077 (phone) | 416.939.5063 (cell) IBM InterConnect 2015
From: Chet Ensign <chet.ensign@oasis-open.org>
To: Arthur Ryman/Toronto/IBM@IBMCA
Date: 11/26/2014 01:36 PM
Subject: Re: Including files in specifications for PROMCODE
HI Arthur,
We don't permit attachments on our wiki as doing so would likely have system
and cost impacts that we can't afford.
For stable URLs, I suggest that you use the PROMCODE SVN system at
https://tools.oasis-open.org/version-control/browse/wsvn/oslc-promcode/?sc=0
. That is what other TCs use for the same purpose.
Best,
/chet
On Tue, Nov 25, 2014 at 12:16 PM, Arthur Ryman <ryman@ca.ibm.com> wrote:
Chet,
We are producing some files as part of the spec. We want to assign stable
URLs to these files. I normally do this at OSLC using wiki attachments.
That capability seems to turned off at PROMCODE.
What is the best practice at OASIS (e.g. for XML schemas, WSDL)?
Can we get file attachments enabled in our wiki? Thank.
_________________________________________________________
Arthur Ryman
Chief Data Officer
SWG | Rational
905.413.3077 (phone) | 416.939.5063 (cell) IBM InterConnect 2015
--
/chet [§]
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-
checklist.html
TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
/chet [§]
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
|