Ticket #39 (closed task: fixed)

Opened 14 years ago

Last modified 13 years ago

Handling identification of attribute authority in MOLES

Reported by: lawrence Owned by: ko23
Priority: blocker Milestone: MOLES_1.2.4
Component: MOLES Version:
Keywords: M06March24 MOLES_Schema Cc: pjkersha

Description

Need to investigate putting attribute authority wsdl in MOLES

Change History

comment:1 Changed 14 years ago by selatham

  • Cc pjkershaw added

comment:2 Changed 14 years ago by ko23

  • Owner changed from ko23 to pjkersha

Shouldn't be a problem, assuming no wierd characters in there, and there's already the expectation of a string to identify the AA. It would be nice if these strings could conform to the guidelines in  http://bscw.badc.rl.ac.uk/bscw/bscw.cgi/d83706/IDIssuesinNDG.doc , or it might be better to declare them as URLs (but not so keen on this).

Also, is there any milage in producing the WSDL URL algorithmically, while identifying the AA by a simple namespace?

comment:3 Changed 14 years ago by lawrence

  • Cc pjkershaw lawrence added; pjkershaw removed

comment:4 Changed 14 years ago by lawrence

  • Cc pjkersha lawrence added; pjkershaw lawrence removed

comment:5 Changed 13 years ago by lawrence

  • Owner changed from pjkersha to ko23
  • Priority changed from desirable to blocker

Kev: This is a blocker for the security ... even if we simply explictly put the role,attributeauthority as elements within NDG-B - and stub - we could make progress. (Or are they there ... if so where?) I'm not too fussed for now whether we expect the AAwsdl to be there, or just a url, but I need it ... (I can put the algorithm in the code for the meantime).

(Changed to Kev, because this is a MOLES issue)

comment:6 Changed 13 years ago by lawrence

  • Cc pjkersha added; pjkersha lawrence removed

Further to my phone call, what I need to be able to do is something like

constraints=AccessControl?(element)

and get back either None or a role,url pair whether I be at the moles level or the granule level. Now I know both bits are there ... but the path to the element is suspiciously different in the granule and the metadata parent ...

comment:7 Changed 13 years ago by ko23

  • Status changed from new to closed
  • Resolution set to fixed

Decision made. As long as Phil warns me about any characters that are not covered in the IDIssues doc, the identification string will be the url of the WSDL.

Note: See TracTickets for help on using tickets.