OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OSLCCORE-28) Update ReSpec to support multiple vocabulary files


James Amsden created OSLCCORE-28:
------------------------------------

             Summary: Update ReSpec to support multiple vocabulary files
                 Key: OSLCCORE-28
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-28
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
            Reporter: James Amsden
            Assignee: James Amsden


It may be useful to keep the OSLC2 and OSLC3 vocabulary contributions separate in the specification so that implementers can more easily distinguish between them. This is especially true for OSLC2 discovery since it defines so many resources that may not be used by future OSLC3 servers that use Link headers on LDPCs for discovery.

An easy way to do this is to update the ReSpec oasis/templates/vocab.html template from:

<section>
<h2>Vocabulary Details</h2>
<p>The namespace URI for this vocabulary is:
<code>{{vocabURI}}</code></p>
<p>{{description}}</p>
{{#if seeAlso}}<strong>See Also:</strong><ul>{{/if}}

To:

<section>
<h2>{{description}}</h2>
<p>The namespace URI for this vocabulary is:
<code>{{vocabURI}}</code></p>
{{#if seeAlso}}<strong>See Also:</strong><ul>{{/if}}

Then simply including two <div> sections in the appendix section will generate an appendix for each file.





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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]