[OASIS Issue Tracker] (OSLCCORE-11) oslc-core-v3.html final editing issues

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59624#comment-59624 ] 

James Amsden commented on OSLCCORE-11:
--------------------------------------

From Chet Ensign:
From the question, can I assume that wgPatentURI is a field set in the document you are drafting and not a feature of the OSLC Core specification itself? Assuming that is the case, then it should probably be blank if not just removed from the content outright. 

OASIS has as much as possible set up its IPR rules to help TCs work together safely and conveniently without participants having to know anything about the patent portfolios of their employers or other players. The TC's chosen IPR mode is recorded on the TC's web page (https://www.oasis-open.org/committees/oslc-core/ipr.php) and we ask anyone with any knowledge of patents that potentially read on the work to contact us with that information so that we can share it on the IPR page. You'll note that for OSLC Core, no one has brought any applicable patents to our attention. 

We do not do patent searches. If others choose to do patent search for their own purposes and bring the results to our attention, we are happy as I say to report what is reported to us but otherwise leave the research and analysis up to the experts outside. 

In the case of OSLC Core, as I said, no one has brought anything to our attention and I don't know of any research that has been done. Might the TC's IPR page url I entered above be the right value there? No knowing the purpose of wePatentURI, I can't say, but it might be an option. It is certainly the page to go to if you want to know whatever we know about the IPR information for the TC. 

Regarding the Citation format, we prepare a citation block when we publish work products from the TCs. They take the form: 

[<cite-label>]
<Work Product title and version # (italicized)>. Edited by <editor name(s)>. <date approved by the TC>. <OASIS Stage Identifier and Revision Number (e.g., OASIS Committee Specification Draft 01)>. <version-specific URI>. Latest version: <latest version symlink URIs>.

I'm not sure if ReSpec can produce that in some way since I am not familiar with how it works generally. If there would be some form-driven way to produce that, let me know and I can work with you on how each of those fields gets specified. 

> oslc-core-v3.html final editing issues
> --------------------------------------
>
>                 Key: OSLCCORE-11
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-11
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: James Amsden
>            Assignee: James Amsden
>            Priority: Minor
>
> 1. Citation format is TBD - what needs to go here?
> 2. wgPatentURI is XXX - are there any patent disclosures that need to be documented?
> 3. The OSLC Core 3.0 Overview figure is missing Attachments
> Do we have the source for these images somewhere?
> 4. Section 5 references Vocabulary Evolution Guidance which been concluded and is no longer active: https://wiki.oasis-open.org/oslc-core/VocabStableURINotes. Should this reference be removed?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)