[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tm-pubsubj] Proposals for next TC deliverables
Bernard, Question: Are you saying that we should isolate the issues that any specification for PSIs will face and develop a generic vocabulary about them? And have that as a deliverable? Hmmm, sounds plausible to me because I think it will keep us from spending time during the development of other deliverables developing those same issues. Sort of a framework of issues that this TC will need to address in the rest of its deliverables? Not that we may provide all the answers but in some cases indicate that the authors of PSIs and users of those PSIs need to be aware of the choices must be made in the construction of a PSI? Then follow those issues as we prepare the other deliverables? (Such as format and use, both of which are of interest to the SBL.) If you have the time, would you mind casting your proposal in terms of requirements? I am mindful of Lars' request that we determine requirements before we start working on deliverables to meet those. I think your post (and some of the earlier ones in this thread) have implicit requirements but making those explicit may help us reach a consensus on what deliverable(s) we need to meet them. Hope you are having a great day! Patrick Bernard Vatant wrote: > This is a follow-up of my last answer to Lars Marius. > > If we stick to what had been our latest decided deliverable structure, the > to-do list is as following: > > D2. Recommendations for Published Subjects Documentation Structure > D3. Recommendations for Published Subjects Management > D4. Recommendations for Published Subjects Use > > We have been struggling for a while with D2, and let a pile of questions on > the backburner. > http://www.oasis-open.org/committees/tm-pubsubj/docs/recommendations/issues > .htm > > Maybe we should not try to deliver generic answers to those issues. But we > could at least agree on the generic vocabulary about them, reviewing what > has been left, based on Lars Marius analysis from May 2002, at: > http://www.oasis-open.org/committees/tm-pubsubj/docs/recommendations/psdoc. > htm > > That would lead to a Deliverable 2 reduced in scope to something like: > "Published Subjects Documentation - General Definitions" > > In which we would not recommend any specific features like format or > metadata, but simply set the generic vocabulary about PSD, to be used in > various use cases. After that, we would focus on addressing those issues > and make specific recommendations for specific domains/scenarios/use cases > in a further set of deliverables, each addressing Structure, Management and > Use for the specific case. The generic structure of those further > deliverables should be described in D2, like: > > - Definition of the scenario > - Legacy to be expressed as PSI > - Objectives and expected benefits of PSI in this scenario > - Users requirements > - PSD Structure in the scenario > - .. following general elements defined in D2 > - .. addressing specific features (metadata, format ...) > - PSD Management > - avalaibility, versioning ... > - PSD Use > - specific recommendation for use in the scenario > > As for the scenarios themselves, here is a list that comes to my mind - not > exhaustive ... > > - PSI for Structured Vocabularies (Thesaurus) > - PSI for Classification Schemes (e.g. Documentation Categories : LoC, DDC > ...) > - PSI for Population of Similar Instances (e.g. ISBN, ISO Country Codes, > NASDAQ ...) > > Those three could be fine to begin with. More difficult could be the > following ones. > > - PSI for Vertical Industry (might include one or more of the previous > ones) > - PSI for Distributed Enterprise (idem) > - PSI for Community of Practice (idem) > > Thoughts? > > Bernard > > > > To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/tm-pubsubj/members/leave_workgroup.php. > > -- Patrick Durusau Director of Research and Development Society of Biblical Literature Patrick.Durusau@sbl-site.org Chair, V1 - Text Processing: Office and Publishing Systems Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model Topic Maps: Human, not artificial, intelligence at work!