Update to DEXLib Dublin Core Usage

["David Price" <david.price@eurostep.com>]

All,

 

I’ve updated DEXLib adding more capability to and explaining usage of the Dublin Core annotation properties. The Help file (dexlib\help\dex\rd-details.xml) on DC has been updated. The OWL files for the dc and dcterms have also been updated (unused terms removed and a few new terms added).  Please let me know if you have any comments on the DC usage.

 

Also, below is how far along this update goes towards addressing the issues raised in Sean Barker’s document. There’s more work to be done but we are making progress.

 

Cheers,

David

 

Phone +44 207 704 0499

Mobile +44 7788 561308

8 Highbury Place, Flat 5

London, UK

N5 1QZ

 

 

REQUIREMENT	STATUS	Comment
1.      To identify the source of the definition data (e.g. PLCS, TRILS, external source, etc.), including any source version.	Closed	dc:source
2.      To identify any IPR against the definition.	Closed	dc:rights and dc:rightsHolder
3.      To identify the editor who entered the data.	Closed	dc:creator
4.      To identify the date the definition was entered.	Closed	dc:created
5.      To identify any DEX or Capability for which the definition was entered.	Open	RD will be references from within the DEX itself. Is this sufficient?
6.      To identify the status of the definition (e.g. in-work, checked, approved, obsolete), together with the approval authority and approval date.	Closed	Broken down into sub-requirements
6a.      To identify the status of the definition (e.g. in-work, checked, approved), together with the approval authority and approval date.	Closed	owl file structure, dateAccepted
6aa.      To identify the approval authority	Open	Is this not always the OASIS PLCS TC?
6b.      To identify the status of the definition (obsolete), together with the approval authority and approval date.	Open	Investigating OWL native capability
7.      To identify any version of the definition	Open	Is CVS versioning of OWL files sufficient?
8.      To identify a definition version as belonging to a configuration baseline of the ontology as a whole.	Open	Is CVS versioning of OWL files sufficient?
9.      To identify any version iteration of the definition.	Closed	owl:VersionInfo
10.  To identify any outstanding issues against the definition.	Closed	Issue capability in dexlib
11.  To record any user classifications against the definition.	Closed	dc:subject
12.  To identify mapping conditions against the definition, including the replacements for classes declared obsolete.	Open	Investigating OWL native capability
DP1) To enable some person or organization to identify the subset of the RD to be used for a particular contract, project or within a particular organization either outside the RDL or in the local extension to the RDL.	Open	Annotation properties do not appear sufficient. Investigating marking, filtering, subset possibilities.