Another look at the data model for launch phase registrations
Gavin Brown <[email protected]>
| Newsgroups | gmane.ietf.provreg |
|---|---|
| Organization | CentralNic Ltd |
| Message-ID | <[email protected]> |
Hi all,
I've been cogitating on the sort of data model that would meet our
requirements, based on the discussions on this list and also with other
people in the trademark world.
I'm proposing a new data model for "sunrise" phases, where applicants
generally have a claim over a string based on a trade mark, which may be
registered with a national authority, or a "common law" trademark such
as a company name.
The model is flexible in that multiple claims may be submitted - as
Jothan suggested previously - and the specific nature of each claim may
be described. Applicants can also signal which authority has registered
their claim by using normal contact objects to identify trademark
offices, company registers, and so on.
Here's a rough description of the model. I've included some example
request frames below. Comments appreciated.
The <create> element of the <extension> element:
* MUST have an <applicationID>, assigned by the server when the
application is created
* MUST have 1 or more <status> codes from the set: [pending,
validated, invalid, cancelled, allocated] (Q: possibly others?)
* MUST have a <phase> from the set [SR, LR] (Q: should we let
servers define further phases?)
* if phase=SR, MAY have one or more <claim> elements. a <claim>:
* MUST have a boolean "preVerified" attribute
* if preVerified=1:
* MUST have a <pvrc> element
* MAY have a <issuer> element. an <issuer>:
* identities a contact object in the
registry
* identifies the name, address, contact
information of the issuing authority
* MAY be created by the client (ie open
approach) or the server (ie closed
approach), depending on server policy
* if preVerified=0:
* MUST have at least one:
* <claimName> identifying the text string
in which the applicant has a claim,
* OR
* <claimNumber> identifying the registered
trade mark
* MAY have a <claimType> from the set [registered,
unregistered] ("unregistered" covers company
names and "common law" trademarks)
* MUST have a <claimCountry> from the ISO
3166-alpha2 set
* MAY have <claimRegion>. a <claimRegion> may
contain the name of a city, state, province or
other region in which the claim is valid
* MAY have an <issuer>. an <issuer>:
* identities a contact object in the
registry
* identifies the name, address, contact
information of the issuing authority
* MAY be created by the client (ie open
approach) or the server (ie closed
approach), depending on server policy
* MAY have a <claimEntitlement> from the
set [owner, successor, licensee] (Q: any
others?)
Example <domain:create> request with an application with pre-verified
claim:
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<create>
<domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<!-- domain create stuff -->
</domain:create>
</create>
<extension>
<create xmlns="[whatever]">
<phase>SR</phase>
<claim preVerified="1">
<pvrc>abc-12345</pvrc>
<issuer>CLEARINGHOUSE-CONTACT-ID</issuer>
</claim>
</create>
</extension>
<clTRID>abc-12345</clTRID>
</command>
</epp>
Example <domain:create> request for a registered trademark with an
application with unverified claim:
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<create>
<domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<!-- domain create stuff -->
</domain:create>
</create>
<extension>
<create xmlns="[whatever]">
<phase>SR</phase>
<claim preVerified="0">
<claimName>Example Corp.</lp>
<clamNumber>TM-1234321</claimNumber>
<claimType>registered</claimType>
<claimCountry>US</claimCountry>
<issuer>USPTO-CONTACT-ID</issuer>
</claim>
</create>
</extension>
<clTRID>abc-12345</clTRID>
</command>
</epp>
Example <domain:create> request for a German company name with an
application with unverified claim:
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<create>
<domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<!-- domain create stuff -->
</domain:create>
</create>
<extension>
<create xmlns="[whatever]">
<phase>SR</phase>
<claim preVerified="0">
<claimName>Example GmbH.</lp>
<claimType>unregistered</claimType>
<claimCountry>DE</claimCountry>
<claimRegion>Bayern</claimRegion>
<issuer>MUNICH-COURT-CONTACT-ID</issuer>
</claim>
</create>
</extension>
<clTRID>abc-12345</clTRID>
</command>
</epp>
Example <domain:create> request for a British company name with an
application containing two different claims:
<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
<command>
<create>
<domain:create xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
<!-- domain create stuff --t>
</domain:create>
</create>
<extension>
<create xmlns="[whatever]">
<phase>SR</phase>
<claim preVerified="0">
<claimName>Example Ltd.</lp>
<claimType>unregistered</claimType>
<claimCountry>UK</claimCountry>
<issuer>COMPANIESHOUSE-CONTACT-ID</issuer>
</claim>
<claim preVerified="1">
<claimName>Example</lp>
<claimType>registered</claimType>
<claimCountry>UK</claimCountry>
<issuer>UKIPO-CONTACT-ID</issuer>
</claim>
</create>
</extension>
<clTRID>abc-12345</clTRID>
</command>
</epp>
--
Gavin Brown
Chief Technology Officer
CentralNic Ltd
Innovative, Reliable and Flexible Registry Services
for ccTLD, gTLD and private domain name registries
https://www.centralnic.com/
CentralNic Ltd is a company registered in England and Wales with company
number 4985780. Registered Offices: 35-39 Moorgate, London, EC2R 6AR.
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg