Dear all,
Heads up for the Wednesday call - I'll circulate the final agenda tomorrow.
Tom
On Sat, Mar 14, 2009 at 02:16:37PM +0100, Thomas Baker wrote:
> Date: Sat, 14 Mar 2009 14:16:37 +0100
> From: Thomas Baker <[log in to unmask]>
> To: DCMI Usage Board <[log in to unmask]>
> Subject: [DC-USAGE] Preliminary agenda - 2009-04-22 Wedneday - 1300 UTC
> Content-Type: text/plain; charset=us-ascii
>
> Dear all,
>
> The telecon poll result [1] shows that at least one person
> has a conflict for each of the days, I am now unavailable on
> 15-16 April, and the main agenda item will be the Accessibility
> property, which rules out 2-9 April, so I have set the date for:
>
> Wednesday 22 April 2009 - 1300 UTC
>
> 0600 Seattle - 0900 New York - 1400 London - 1500 Berlin - 2200 Tokyo - 2300 Canberra
>
> Tom
>
> [1] http://doodle.com/4xmnfd4bis8viina
>
> ----------------------------------------------------------------------
>
> *** PRELIMINARY AGENDA ***
>
> Usage Board telecon - Wednesday 22 April 2009 - 1300 UTC
>
> -- http://www.timeanddate.com/worldclock/fixedtime.html?month=04&day=22&year=2009&hour=13&min=00&sec=0&p1=0
> 0600 Seattle - 0900 New York - 1400 London - 1500 Berlin - 2200 Tokyo - 2300 Canberra
>
> This agenda: http://dublincore.org:8080/usage/minutes/2009-04-22.dcub-telecon-agenda.html
>
> Expected: Tom Baker, Julie Allinson, Pete Johnston,
> Akira Miyazawa, Joe Tennis, Andrew Wilson
>
> Regrets: Stefanie Ruehle
>
> Dial-in Number: 1-219-509-8020
> Participant Access Code: 334034
> Links
> -- http://www.jiscmail.ac.uk/lists/dc-usage.html - mailing list
> -- http://dublincore.org/usageboardwiki/ - wiki
>
> ----------------------------------------------------------------------
> Previous telecon
>
> Report - http://dublincore.org/usage/minutes/2009-02-26.dcub-telecon-report.html
>
> ----------------------------------------------------------------------
> Profile Review Criteria (Tom)
> -- http://dublincore.org:8080/documents/2009/01/05/profile-review-criteria/
>
> RESOLVED: to add a sentence to section 2.4.2 explicitly requiring the reviewer
> to check for multiple statement templates with shared property list
> constraints. Criteria should reflect that a property list constraint should be
> used once only within a description template.
> -- DONE see http://dublincore.org/documents/2009/03/02/profile-review-criteria/
>
> ACTION 2009-02-26: Pete to draft a sentence for section 2.4.2.
> -- DONE see http://dublincore.org/documents/2009/03/02/profile-review-criteria/
>
> ACTION 2009-02-26: Tom to create a new version of the criteria.
> at http://dublincore.org:8080/documents/2009/03/02/profile-review-criteria/.
> -- DONE see http://dublincore.org/documents/2009/03/02/profile-review-criteria/
>
> ACTION 2009-02-26: Tom to add sentence to review to the effect that
> the criteria have been made more explicit on this point, citing
> the 2009-03-02 criteria.
> -- DONE see http://dublincore.org/usage/reviews/2009/swap/index.shtml
>
> ISSUE 2008-09-21: Criteria should reflect that a property list
> constraint should be used once only within a description
> template. Guidance should be given to application profile
> creators on this issue, e.g. using the subject example where
> an application profile wants to require an LCSH term and have
> an option to add a free tag or a different vocabulary term.
> Consider inclusion of this guidance on the current proposed
> guidelines for application profiles. One option is to make
> the constraint human-readable only.
>
> ----------------------------------------------------------------------
> Review of Scholarly Works Application Profile (SWAP)
>
> RESOLVED 2009-02-26: The text about the "discrepancy" [1] should
> be reworded in more positive terms. The message should be
>
> -- that SWAP conforms in all ways but one
> -- that the one point of discrepancy (if that is the right word) has had the
> beneficial effect of highlighting an issue of general significance in the
> model - one of interest not just for SWAP but in the Architecture context
> as well.
>
> ACTION 2009-02-26: Tom to propose alternative explanatory
> text on Friday for discussion and approval on the list.
> -- DONE see http://dublincore.org/usage/reviews/2009/swap/
>
> ACTION 2009-02-26: Tom to propose a revised wording for the news item
> consistent with the above.
> -- DONE see http://dublincore.org/news/2009/
>
> ----------------------------------------------------------------------
> Review of DCMI Libraries properties (Stefanie)
>
> 2009-09-23 Berlin conclusions:
>
> -- Date Captured: Proposal does not provide well-defined notion
> of "captured", but creating a new term dcterms:captured as a
> subproperty of dcterms:created would be possible.
>
> -- Holding Location: suggestion to use existing term
> agls:availability was accepted by Libraries AP Task Force.
>
> -- Version: dcterms:version could be created if revised
> definition were proposed to the Usage Board.
>
> 2009-02-26: Stefanie has asked the Task Force to clarify whether they
> wish to propose new properties.
>
> ----------------------------------------------------------------------
> Review of Accessibility properties (Andrew)
>
> 2009-09-23 Berlin conclusions:
>
> RESOLVED: Co-ordinate development of property and VES with
> AGLS. Andrew to shepherd.
>
> Step 1: Liaise with AGLS re co-ordinated publication of
> property dcterms:accessibility and AGLS VES.
>
> Step 2: UB to ask AGLS to confirm desired VES.
>
> Step 3: UB and AGLS to jointly agree natural language
> definition and formal range to express semantics of
> resource-valuerelationship. (Note: currently apparent
> overlap between values for "accessibility" and "accessMode"
> properties.)
>
> Goal: Co-ordinated publication of DCMI property and AGLS VES
> along with simple usable documentation.
>
> 2009-02-26: The AGLS Working Group agrees with the approach proposed.
> Andrew will report in the next call.
>
> ----------------------------------------------------------------------
> Comment of dcterms:creator
>
> RESOLVED 2009-02-26: General consensus that the comment for
> the property "creator" -- "Typically, the name of a Creator
> should be used to indicate the entity" -- should be dropped for
> dcterms:creator (but retained for dc:creator). Rationale: the
> comment creates confusion for a property with a formal range of
> object.
>
> ACTION 2009-02-26: Pete to draft a proposal to drop the comment
> for dcterms:creator and submit to list for discussion and decision
> on future telecons.
>
> ----------------------------------------------------------------------
> Next telecon - May
>
> -- See poll at ...
>
> -- Possible time slots (for discussion):
> 2100 UTC - 1400 Seattle / 1700 New York / 2200 London / 2300 Berlin / 0600 Tokyo+ / 0700 Canberra+
> 1300 UTC - 0600 Seattle / 0900 New York / 1400 London / 1500 Berlin / 2200 Tokyo / 2300 Canberra
>
> -- Agenda:
> -- Accessibility properties (Andrew)
> -- dc:creator comment
> -- Libraries terms (Stefanie)
>
> ----------------------------------------------------------------------
> Ongoing actions and issues...
>
> ACTION 2008-09-21: Joe and Andrew to continue work on Coverage.
>
> ACTION 2008-09-21: Tom (and Mikael) to continue work on Simple Dublin Core.
>
> ACTION 2008-09-21: Tom to amend the naming policy (DCMI
> names should not differ only with respect to case).
>
> ACTION 2008-09-21: Andrew and Julie to write a one-page guideline on
> creating new terms that comply with the DCAM (replaces the
> original action).
>
> ACTION 2008-09-21: Tom to correct RDF schemas of DCMI Metadata
> Terms to use blank node with publisher.
>
> ISSUE 2008-09-21: Is it good practice to provide a
> Value VES in addition to a Value URI, or is it arguably
> redundant? (Example: "Entity Type" under "Scholarly Work"
> in SWAP, http://dublincore.org/scholarwiki/SWAPDSP).
> Guidance on this point may belong in the application
> profile guidelines.
>
> ISSUE 2008-09-21: Rendering of Wiki pages using the DSP
> syntax does not capture all of the DSP detail and uses
> different labelling. It would be useful to hyperlink
> labels in the DSP rendered page to the DSP documentation
> itself. Also, to hyperlink description template labels
> within the wiki page itself, e.g. creator to agent
> description.
>
> --
> Thomas Baker <[log in to unmask]>
>
--
Thomas Baker <[log in to unmask]>
|
