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: Simple titles/names for our specs

I just wanted to put this out there as an approach to naming specifications, namely about including the definition of OSLC in the name.  I think this is overly verbose, confusing and really doesn't add anything.

Take for example the Link guidance work: http://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/supporting-docs/link-guidance.html
Title: "Open Services for Lifecycle Collaboration Link Guidance 3.0"
        (I'm not picking on Ian and Jim, just using as an example)

Then take attachments work: http://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/specs/attachments-v3.html
Title: "OSLC Attachments 3.0"

Especially looking at them in context, it is hard to understand what linking guidance is about from the title loaded.  If someone doesn't know what OSLC is, lands on one of these docs for the first time ... there will be a chance in the intro or references to get the full definition of it.

Any disagreement with using the "compacted" form?

We don't spell out OASIS everywhere, just saying.

Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web ->

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