Re: [tm-pubsubj] Proposal of new deliverable structure

[Bernard Vatant <bernard.vatant@mondeca.com>]

Folks

I did not have much feedback about that proposal so far.
Without comments over the week-end, I'll submit it to vote on Monday.

Bernard

----- Message d'origine -----
De : "Bernard Vatant" <bernard.vatant@mondeca.com>
À : "tm-pubsubj" <tm-pubsubj@lists.oasis-open.org>
Envoyé : lundi 27 mai 2002 17:00
Objet : [tm-pubsubj] Proposal of new deliverable structure


> In Barcelona meeting, it was proposed to split the Deliverable 1 into two parts (see
> minutes) . For those who were absent - and even for those who were present, I will sum
up
> here the rationale of this change. I suggest we let this week for possible debate and
> clarification of this proposal, and then to proceed next week to a formal vote on it.
>
> Rationale:
>
> 1. We have figured in the past months, in the process of discussion around this first
> deliverable (psdoc), that it raised a lot of issues linked to the constituents,
structure
> and format of a PSD.
> 2. It seems possible and even wishable to make distinct those issues from basic
> vocabulary, requirements and recommendations about what must, should, may be *a PSI*.
> 3. Concerns about the credibility of our process make us eager to deliver something
ASAP.
>
> <proposal>
>
> 1. Next TC deliverable will be called : "Published Subjects : General Requirements and
> Recommendations". This deliverable would include:
>
> - Primer (gentle introduction)
> - Basic Requirements and Recommendations (subject to rewording)
>
>     Req#1 :  A Published Subject Identifier must be an URI.
>     Req#2 :  When a Published Subject Identifier is an URL, it must resolve to an human
> interpretable Published Subject Indicator.
>
>     Rec#1 :  A Published Subject Indicator should provide some way to identify its
> publisher.
>     Rec#2 : Other metadata (than the publisher) may be specified (list of such metadata
> TBE)
>     Rec#3 : The Published Subject Indicator should either have a machine-processable
> structure, or link to a resource providing             machine-processable expression of
> assertions about the subject (or both)
>
> - Example
> - Definitions (when needed) or/and references to ISO 13250, glossary (if necessary)
> - Generic (paradigmatic) PSIs
>
> 2 . The deliverable "Published Subject Documentation : Requirements and Recommendations"
> would then deal only with structure, format and packaging issues, and will be postponed
> until the previous one is delivered, letting time to discuss ongoing issues.
>
> </proposal>
>
> Thanks for your comments
>
> Bernard
>
> -------------------------------------------------------------------
> Bernard Vatant
> Consultant - Mondeca
> www.mondeca.com
> Chair - OASIS TM PubSubj Technical Committee
> www.oasis-open.org/committees/tm-pubsubj/
> -------------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>