[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [oslc-promcode] Re: Including files in specifications for PROMCODE
Chet, Thanks for the description of the process. I am glad to see that this process includes artifacts such as schemas, wsdl, etc. In our TC, we need to publish an RDF vocabulary (and some other RDF files), as will other OSLC TCs. The W3C has published Best Practices for this [1]. The only novel requirement here is that we need to support HTTP content negotiation. This means that we need to serve up different content types for a given URI, based on an Accept header. We've implemented this at OSLC and jazz.net which both use an Apache web server. We created a .htaccess file to generate 303 redirects, which is Recipe 3 [2]. We'd deploy the .htaccess file into our root directory: http://docs.oasis-open.org/oslc-promcode/ Let me be concrete. Suppose we assign the following URI to our RDF vocabulary: http://docs.oasis-open.org/oslc-promcode/ns/core When the Accept header contains text/html or application/xhtml+xml we respond with the content at: http://docs.oasis-open.org/oslc-promcode/ns/core.html When the Accept header contains application/rdf+xml we respond with the content at: http://docs.oasis-open.org/oslc-promcode/ns/core.rdf When the Accept header contains text/turtle we respond with the content at: http://docs.oasis-open.org/oslc-promcode/ns/core.ttl [1] http://www.w3.org/TR/swbp-vocab-pub/ [2] http://www.w3.org/TR/swbp-vocab-pub/#recipe3 _________________________________________________________ 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 Cc: Kazuhiro Funakoshi <k-f@bk.jp.nec.com>, "oslc-promcode@lists.oasis-open.org" <oslc-promcode@lists.oasis-open.org> Date: 12/02/2014 10:00 AM Subject: Re: [oslc-promcode] Re: Including files in specifications for PROMCODE Hi Arthur, Here is the process that TCs follow to publish their work. Initially the TC prepares a working draft of the specification. This can be a combination of draft documents, schemas, wsdl files, etc. The TC uses its document repository on its web page, its wiki and its svn to store these elements. TCs do not have write privileges to docs.oasis-open.org. When the TC is ready to assemble the content into an initial working draft of the specification, someone - usually the editor or the chair - requests a starter document from TC Administration using the support request at https://www.oasis-open.org/resources/tc-admin-requests/work-product-registration-template-request . Among other things this request does is let us work out with you all any details about the final urls and organization of the spec when it is published. The TC uses this starter document to prepare the working draft of the committee spec. We can provide templates in doc or odf format. For TCs that want to publish from their own source in xml, latex, etc. we'll work with you to use this template as a guide to publishing the final form needed. When the TC is ready to publish its first Committee Specification Draft and, if it chooses, release it for its first public review, it passes a motion to approve those steps in a meeting of the TC or by a ballot. The language you can use for the motion can be puled from the template at https://www.oasis-open.org/committees/download.php/53768. After that approval is made, someone submits a request to publish the CSD ( https://www.oasis-open.org/resources/tc-admin-requests/committee-specification-draft-creation-upload-request ) and, if desired, the request to start a public review ( https://www.oasis-open.org/resources/tc-admin-requests/committee-specification-draft-creation-upload-request ). TC Administration will then takes your working draft as approved and prepares the corresponding HTML and PDF versions and loads all the components to docs.oasis-open.org. We'll notify the TC when its ready and if a public review is to be started, announce that publicly as well. There are further steps - handling comments from public review, approving a Committee Specification by Special Majority Vote, etc. They are explained here -> https://www.oasis-open.org/resources/tcadmin/tc-process-how-to-guide-introduction . This should get you started though. Best regards, /chet On Tue, Dec 2, 2014 at 8:15 AM, Arthur Ryman <ryman@ca.ibm.com> wrote: Chet - As I understand it, our TC decides when to post documents at docs.oasis-open.org/oslc-promcode/.... Therefore we can post drafts there. Kaz & TC I think our documents should use the permanent URLs. We can use SVN to work on documents. I think we should post stable versions of documents at docs.oasis-open.org/oslc-promcode/... and always include status information in them to indicate if they are drafts, final, etc. _________________________________________________________ Arthur Ryman Chief Data Officer SWG | Rational 905.413.3077 (phone) | 416.939.5063 (cell) IBM InterConnect 2015 From: Kazuhiro Funakoshi <k-f@bk.jp.nec.com> To: Chet Ensign <chet.ensign@oasis-open.org>, Arthur Ryman/Toronto/IBM@IBMCA Cc: "oslc-promcode@lists.oasis-open.org" <oslc-promcode@lists.oasis-open.org> Date: 12/01/2014 08:11 PM Subject: RE: [oslc-promcode] Re: Including files in specifications for PROMCODE Sent by: <oslc-promcode@lists.oasis-open.org> 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. Best, /chet 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 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 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]