Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » OHF » authorPerson metadata not in XCN format
authorPerson metadata not in XCN format [message #38139] Wed, 05 December 2007 18:39 Go to next message
Jesse Pangburn is currently offline Jesse PangburnFriend
Messages: 166
Registered: July 2009
Senior Member
Hi all,
According to an email Bill just sent, the public registry is now changing
the way the authorPerson attribute must be formatted. From his email:
*************
2) There has been a problem discovered with the formatting of the
authorPerson attribute (Submission Set and DocumentEntry). The XDS profile
requires this attribute to be in XCN format. See 4.1.7 Document Definition
Metadata for the definition of XCN. The update affects these things

The metadata validator has been updated (in xdstest2, the Public Registry,
and the web tool)
The metadata in the testkit has been updated
Test data loaded into the Public Registry
This change has been made to the Public Registry!!!
*************

I tried a provide and register from the bridge and it is indeed failing
now. The registry returns:
***************
<rs:RegistryError codeContext="ExtrinsicObject urn:uuid:727134ec-
b26a-42ae-d4ad-000f1f9e1110 has a author type classification
(classificationScheme=urn:uuid:93606bcf-9494-43ec-9b4e-a7748 d1a838d)
with authorPerson slot that is not in XCN format. The value found was
11111111^Wiseman^Bernard^^Sr.^Dr.^^^&amp;1.3.5.35.1.4436 .7&amp;ISO "
errorCode="XDSRegistryMetadataError" location="MetadataValidator.java"
severity="Error" />
***************

thanks,
Jesse
Re: authorPerson metadata not in XCN format [message #38735 is a reply to message #38139] Mon, 10 December 2007 18:42 Go to previous messageGo to next message
Jesse Pangburn is currently offline Jesse PangburnFriend
Messages: 166
Registered: July 2009
Senior Member
Hi all,
Just an update on this. Due to various points of view on this currently
being discussed, Bill has relaxed this restriction on the public registry
again. For now, you should be able to run the provide and registry
transaction with the current version of the bridge just fine. I haven't
tried myself, but Bill says it's done.

thanks,
Jesse

Jesse Pangburn wrote:

> Hi all,
> According to an email Bill just sent, the public registry is now changing
> the way the authorPerson attribute must be formatted. From his email:
> *************
> 2) There has been a problem discovered with the formatting of the
> authorPerson attribute (Submission Set and DocumentEntry). The XDS profile
> requires this attribute to be in XCN format. See 4.1.7 Document Definition
> Metadata for the definition of XCN. The update affects these things

> The metadata validator has been updated (in xdstest2, the Public Registry,
> and the web tool)
> The metadata in the testkit has been updated
> Test data loaded into the Public Registry
> This change has been made to the Public Registry!!!
> *************

> I tried a provide and register from the bridge and it is indeed failing
> now. The registry returns:
> ***************
> <rs:RegistryError codeContext="ExtrinsicObject urn:uuid:727134ec-
> b26a-42ae-d4ad-000f1f9e1110 has a author type classification
> (classificationScheme=urn:uuid:93606bcf-9494-43ec-9b4e-a7748 d1a838d)
> with authorPerson slot that is not in XCN format. The value found was
> 11111111^Wiseman^Bernard^^Sr.^Dr.^^^&amp;1.3.5.35.1.4436 .7&amp;ISO "
> errorCode="XDSRegistryMetadataError" location="MetadataValidator.java"
> severity="Error" />
> ***************

> thanks,
> Jesse
Re: authorPerson metadata not in XCN format [message #38767 is a reply to message #38735] Mon, 10 December 2007 23:41 Go to previous message
No real name is currently offline No real nameFriend
Messages: 292
Registered: July 2009
Senior Member
yep. And guess who is the lucky soul that gets to write the change
proposal edit to IHE for this ;-)

- Sarah



Jesse Pangburn wrote:
> Hi all,
> Just an update on this. Due to various points of view on this currently
> being discussed, Bill has relaxed this restriction on the public
> registry again. For now, you should be able to run the provide and
> registry transaction with the current version of the bridge just fine.
> I haven't tried myself, but Bill says it's done.
>
> thanks,
> Jesse
>
> Jesse Pangburn wrote:
>
>> Hi all,
>> According to an email Bill just sent, the public registry is now
>> changing the way the authorPerson attribute must be formatted. From
>> his email:
>> *************
>> 2) There has been a problem discovered with the formatting of the
>> authorPerson attribute (Submission Set and DocumentEntry). The XDS
>> profile requires this attribute to be in XCN format. See 4.1.7
>> Document Definition Metadata for the definition of XCN. The update
>> affects these things
>
>
>> The metadata validator has been updated (in xdstest2, the Public
>> Registry, and the web tool) The metadata in the testkit has been
>> updated Test data loaded into the Public Registry This change has been
>> made to the Public Registry!!!
>> *************
>
>
>> I tried a provide and register from the bridge and it is indeed
>> failing now. The registry returns:
>> ***************
>> <rs:RegistryError codeContext="ExtrinsicObject urn:uuid:727134ec-
>> b26a-42ae-d4ad-000f1f9e1110 has a author type classification
>> (classificationScheme=urn:uuid:93606bcf-9494-43ec-9b4e-a7748 d1a838d)
>> with authorPerson slot that is not in XCN format. The value found was
>> 11111111^Wiseman^Bernard^^Sr.^Dr.^^^&amp;1.3.5.35.1.4436 .7&amp;ISO "
>> errorCode="XDSRegistryMetadataError" location="MetadataValidator.java"
>> severity="Error" />
>> ***************
>
>
>> thanks,
>> Jesse
>
>
>
Re: authorPerson metadata not in XCN format [message #583758 is a reply to message #38139] Mon, 10 December 2007 18:42 Go to previous message
Jesse Pangburn is currently offline Jesse PangburnFriend
Messages: 166
Registered: July 2009
Senior Member
Hi all,
Just an update on this. Due to various points of view on this currently
being discussed, Bill has relaxed this restriction on the public registry
again. For now, you should be able to run the provide and registry
transaction with the current version of the bridge just fine. I haven't
tried myself, but Bill says it's done.

thanks,
Jesse

Jesse Pangburn wrote:

> Hi all,
> According to an email Bill just sent, the public registry is now changing
> the way the authorPerson attribute must be formatted. From his email:
> *************
> 2) There has been a problem discovered with the formatting of the
> authorPerson attribute (Submission Set and DocumentEntry). The XDS profile
> requires this attribute to be in XCN format. See 4.1.7 Document Definition
> Metadata for the definition of XCN. The update affects these things

> The metadata validator has been updated (in xdstest2, the Public Registry,
> and the web tool)
> The metadata in the testkit has been updated
> Test data loaded into the Public Registry
> This change has been made to the Public Registry!!!
> *************

> I tried a provide and register from the bridge and it is indeed failing
> now. The registry returns:
> ***************
> <rs:RegistryError codeContext="ExtrinsicObject urn:uuid:727134ec-
> b26a-42ae-d4ad-000f1f9e1110 has a author type classification
> (classificationScheme=urn:uuid:93606bcf-9494-43ec-9b4e-a7748 d1a838d)
> with authorPerson slot that is not in XCN format. The value found was
> 11111111^Wiseman^Bernard^^Sr.^Dr.^^^&amp;1.3.5.35.1.4436 .7&amp;ISO "
> errorCode="XDSRegistryMetadataError" location="MetadataValidator.java"
> severity="Error" />
> ***************

> thanks,
> Jesse
Re: authorPerson metadata not in XCN format [message #583779 is a reply to message #38735] Mon, 10 December 2007 23:41 Go to previous message
No real name is currently offline No real nameFriend
Messages: 292
Registered: July 2009
Senior Member
yep. And guess who is the lucky soul that gets to write the change
proposal edit to IHE for this ;-)

- Sarah



Jesse Pangburn wrote:
> Hi all,
> Just an update on this. Due to various points of view on this currently
> being discussed, Bill has relaxed this restriction on the public
> registry again. For now, you should be able to run the provide and
> registry transaction with the current version of the bridge just fine.
> I haven't tried myself, but Bill says it's done.
>
> thanks,
> Jesse
>
> Jesse Pangburn wrote:
>
>> Hi all,
>> According to an email Bill just sent, the public registry is now
>> changing the way the authorPerson attribute must be formatted. From
>> his email:
>> *************
>> 2) There has been a problem discovered with the formatting of the
>> authorPerson attribute (Submission Set and DocumentEntry). The XDS
>> profile requires this attribute to be in XCN format. See 4.1.7
>> Document Definition Metadata for the definition of XCN. The update
>> affects these things
>
>
>> The metadata validator has been updated (in xdstest2, the Public
>> Registry, and the web tool) The metadata in the testkit has been
>> updated Test data loaded into the Public Registry This change has been
>> made to the Public Registry!!!
>> *************
>
>
>> I tried a provide and register from the bridge and it is indeed
>> failing now. The registry returns:
>> ***************
>> <rs:RegistryError codeContext="ExtrinsicObject urn:uuid:727134ec-
>> b26a-42ae-d4ad-000f1f9e1110 has a author type classification
>> (classificationScheme=urn:uuid:93606bcf-9494-43ec-9b4e-a7748 d1a838d)
>> with authorPerson slot that is not in XCN format. The value found was
>> 11111111^Wiseman^Bernard^^Sr.^Dr.^^^&amp;1.3.5.35.1.4436 .7&amp;ISO "
>> errorCode="XDSRegistryMetadataError" location="MetadataValidator.java"
>> severity="Error" />
>> ***************
>
>
>> thanks,
>> Jesse
>
>
>
Previous Topic:Connectathon ATNA Certificates for OHF users
Next Topic:non stored query error against NIST server
Goto Forum:
  


Current Time: Sat Dec 20 06:35:05 GMT 2014

Powered by FUDForum. Page generated in 0.02078 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software